mirror of
https://github.com/hanzoai/next.js.git
synced 2026-09-24 17:00:51 +00:00
docs: remove PPR adapter page from Pages Router (#96316)
Do not mirror PPR for Pages Router, and other adjustments.
This commit is contained in:
@@ -17,6 +17,8 @@ When invoking entrypoints, adapters pass a `ctx` object to the Next.js handler.
|
||||
- **`ctx.waitUntil`**: a function that accepts a promise. Use this to keep the serverless function alive after the response is sent, allowing background work like cache revalidation to complete.
|
||||
- **`requestMeta.onCacheEntryV2`** (set via `addRequestMeta`): a callback that fires when a cache entry is generated or looked up. Use this to observe all cache operations (not just PPR) and propagate cache updates to your platform's storage backend. This callback fires on the instance that handled the request. For multi-instance deployments, your adapter should propagate updates to shared storage. See [How Revalidation Works](/docs/app/guides/how-revalidation-works) for coordination patterns.
|
||||
|
||||
<AppOnly>
|
||||
|
||||
## PPR Chain Headers
|
||||
|
||||
In the [prerenders output type](/docs/app/api-reference/adapters/output-types#prerenders-outputsprerenders), `pprChain.headers` contains the headers needed for the [resume protocol](/docs/app/api-reference/adapters/implementing-ppr-in-an-adapter). Specifically, it contains `{ 'next-resume': '1' }`.
|
||||
@@ -28,3 +30,5 @@ When your adapter detects a PPR-enabled route with a cached static shell:
|
||||
3. The handler will render only the deferred Suspense boundaries and stream the result.
|
||||
|
||||
> **Good to know:** In standard `next start`, the server handles both the shell and dynamic render in a single pass automatically. The resume protocol is useful for adapter-based deployments and CDN-to-origin architectures that want to serve the shell separately. See the [PPR Platform Guide](/docs/app/guides/ppr-platform-guide) for the full implementation context.
|
||||
|
||||
</AppOnly>
|
||||
|
||||
@@ -5,6 +5,8 @@ description: Build deployment adapters for Next.js platforms and infrastructure.
|
||||
|
||||
Use this section to build and validate deployment adapters that integrate with the Next.js build and runtime model.
|
||||
|
||||
<AppOnly>
|
||||
|
||||
- [Configuration](/docs/app/api-reference/adapters/configuration)
|
||||
- [Creating an Adapter](/docs/app/api-reference/adapters/creating-an-adapter)
|
||||
- [API Reference](/docs/app/api-reference/adapters/api-reference)
|
||||
@@ -17,3 +19,20 @@ Use this section to build and validate deployment adapters that integrate with t
|
||||
- [Routing Information](/docs/app/api-reference/adapters/routing-information)
|
||||
- [Use Cases](/docs/app/api-reference/adapters/use-cases)
|
||||
- [Supporting Immutable Static Assets](/docs/app/api-reference/adapters/immutable-static-assets)
|
||||
|
||||
</AppOnly>
|
||||
|
||||
<PagesOnly>
|
||||
|
||||
- [Configuration](/docs/pages/api-reference/adapters/configuration)
|
||||
- [Creating an Adapter](/docs/pages/api-reference/adapters/creating-an-adapter)
|
||||
- [API Reference](/docs/pages/api-reference/adapters/api-reference)
|
||||
- [Testing Adapters](/docs/pages/api-reference/adapters/testing-adapters)
|
||||
- [Routing with `@next/routing`](/docs/pages/api-reference/adapters/routing-with-next-routing)
|
||||
- [Runtime Integration](/docs/pages/api-reference/adapters/runtime-integration)
|
||||
- [Invoking Entrypoints](/docs/pages/api-reference/adapters/invoking-entrypoints)
|
||||
- [Output Types](/docs/pages/api-reference/adapters/output-types)
|
||||
- [Routing Information](/docs/pages/api-reference/adapters/routing-information)
|
||||
- [Use Cases](/docs/pages/api-reference/adapters/use-cases)
|
||||
|
||||
</PagesOnly>
|
||||
|
||||
@@ -1,7 +0,0 @@
|
||||
---
|
||||
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. */}
|
||||
Reference in New Issue
Block a user