Recipe-app main

This commit is contained in:
2026-04-09 09:14:39 +02:00
commit 962f4e4be5
10015 changed files with 2445177 additions and 0 deletions
@@ -0,0 +1,7 @@
---
title: Configuration
description: Configure `adapterPath` or `NEXT_ADAPTER_PATH` to use a custom deployment adapter.
source: app/api-reference/adapters/configuration
---
{/* DO NOT EDIT. The content of this doc is generated from the source above. To edit the content of this page, navigate to the source page in your editor. You can use the <PagesOnly>Content</PagesOnly> component to add content that is specific to the Pages Router. Any shared content should not be wrapped in a component. */}
@@ -0,0 +1,7 @@
---
title: Creating an Adapter
description: Create an adapter module that implements the `NextAdapter` interface.
source: app/api-reference/adapters/creating-an-adapter
---
{/* DO NOT EDIT. The content of this doc is generated from the source above. To edit the content of this page, navigate to the source page in your editor. You can use the <PagesOnly>Content</PagesOnly> component to add content that is specific to the Pages Router. Any shared content should not be wrapped in a component. */}
@@ -0,0 +1,7 @@
---
title: API Reference
description: Reference for `modifyConfig` and `onBuildComplete` in the `NextAdapter` interface.
source: app/api-reference/adapters/api-reference
---
{/* DO NOT EDIT. The content of this doc is generated from the source above. To edit the content of this page, navigate to the source page in your editor. You can use the <PagesOnly>Content</PagesOnly> component to add content that is specific to the Pages Router. Any shared content should not be wrapped in a component. */}
@@ -0,0 +1,7 @@
---
title: Testing Adapters
description: Validate adapters with the Next.js compatibility test harness and custom lifecycle scripts.
source: app/api-reference/adapters/testing-adapters
---
{/* DO NOT EDIT. The content of this doc is generated from the source above. To edit the content of this page, navigate to the source page in your editor. You can use the <PagesOnly>Content</PagesOnly> component to add content that is specific to the Pages Router. Any shared content should not be wrapped in a component. */}
@@ -0,0 +1,7 @@
---
title: Routing with @next/routing
description: Use `@next/routing` to apply Next.js route matching behavior in adapters.
source: app/api-reference/adapters/routing-with-next-routing
---
{/* DO NOT EDIT. The content of this doc is generated from the source above. To edit the content of this page, navigate to the source page in your editor. You can use the <PagesOnly>Content</PagesOnly> component to add content that is specific to the Pages Router. Any shared content should not be wrapped in a component. */}
@@ -0,0 +1,7 @@
---
title: Implementing PPR in an Adapter
description: Implement Partial Prerendering support in an adapter using fallback output and cache hooks.
source: app/api-reference/adapters/implementing-ppr-in-an-adapter
---
{/* DO NOT EDIT. The content of this doc is generated from the source above. To edit the content of this page, navigate to the source page in your editor. You can use the <PagesOnly>Content</PagesOnly> component to add content that is specific to the Pages Router. Any shared content should not be wrapped in a component. */}
@@ -0,0 +1,7 @@
---
title: Runtime Integration
description: Understand how build-time adapters and runtime cache interfaces work together.
source: app/api-reference/adapters/runtime-integration
---
{/* DO NOT EDIT. The content of this doc is generated from the source above. To edit the content of this page, navigate to the source page in your editor. You can use the <PagesOnly>Content</PagesOnly> component to add content that is specific to the Pages Router. Any shared content should not be wrapped in a component. */}
@@ -0,0 +1,7 @@
---
title: Invoking Entrypoints
description: Invoke Node.js and Edge build entrypoints with adapter runtime context.
source: app/api-reference/adapters/invoking-entrypoints
---
{/* DO NOT EDIT. The content of this doc is generated from the source above. To edit the content of this page, navigate to the source page in your editor. You can use the <PagesOnly>Content</PagesOnly> component to add content that is specific to the Pages Router. Any shared content should not be wrapped in a component. */}
@@ -0,0 +1,7 @@
---
title: Output Types
description: Reference for all build output types exposed to adapters.
source: app/api-reference/adapters/output-types
---
{/* DO NOT EDIT. The content of this doc is generated from the source above. To edit the content of this page, navigate to the source page in your editor. You can use the <PagesOnly>Content</PagesOnly> component to add content that is specific to the Pages Router. Any shared content should not be wrapped in a component. */}
@@ -0,0 +1,7 @@
---
title: Routing Information
description: Reference for routing phases and route fields exposed in `onBuildComplete`.
source: app/api-reference/adapters/routing-information
---
{/* DO NOT EDIT. The content of this doc is generated from the source above. To edit the content of this page, navigate to the source page in your editor. You can use the <PagesOnly>Content</PagesOnly> component to add content that is specific to the Pages Router. Any shared content should not be wrapped in a component. */}
@@ -0,0 +1,7 @@
---
title: Use Cases
description: Common patterns and examples for deployment adapter implementations.
source: app/api-reference/adapters/use-cases
---
{/* DO NOT EDIT. The content of this doc is generated from the source above. To edit the content of this page, navigate to the source page in your editor. You can use the <PagesOnly>Content</PagesOnly> component to add content that is specific to the Pages Router. Any shared content should not be wrapped in a component. */}
@@ -0,0 +1,7 @@
---
title: Adapters
description: Build deployment adapters for Next.js platforms and infrastructure.
source: app/api-reference/adapters
---
{/* DO NOT EDIT. The content of this doc is generated from the source above. To edit the content of this page, navigate to the source page in your editor. You can use the <PagesOnly>Content</PagesOnly> component to add content that is specific to the Pages Router. Any shared content should not be wrapped in a component. */}