Unverified Commit 8520404c authored by Sam Ko's avatar Sam Ko Committed by GitHub

docs(ppr): remove v14 mention for ppr (#71498)

## Why?

For PPR (experimental), user's should just opt to use v15 canary if they
want to try out PPR. Removing the v14 mention reduces this confusion.

- x-ref:
https://vercel.slack.com/archives/C05KYT5S9FF/p1729264052080029?thread_ts=1729263181.989139&cid=C05KYT5S9FF
parent db301b0e
......@@ -81,33 +81,6 @@ export default function Page() {
> - `experimental_ppr` will apply to all children of the route segment, including nested layouts and pages. You don't have to add it to every file, only the top segment of a route.
> - To disable PPR for children segments, you can set `experimental_ppr` to `false` in the child segment.
### Enabling PPR (Version 14)
For version 14, you can enable it by adding the [`ppr`](/docs/app/api-reference/next-config-js/ppr) option to your `next.config.js` file. You must also be on the canary version to enable PPR. This will apply to all routes in your application:
```ts filename="next.config.ts" switcher
import type { NextConfig } from 'next'
const nextConfig: NextConfig = {
experimental: {
ppr: true,
},
}
export default nextConfig
```
```js filename="next.config.js" switcher
/** @type {import('next').NextConfig} */
const nextConfig = {
experimental: {
ppr: true,
},
}
module.exports = nextConfig
```
| Version | Changes |
| --------- | ------------------------------------------- |
| `v15.0.0` | experimental `incremental` value introduced |
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment