Unverified Commit c9530e75 authored by マルコメ's avatar マルコメ Committed by GitHub

docs(ppr): remove v14 PPR config description (#71592)

# Description
Removed the v14 mention [PPR
docs](https://nextjs.org/docs/canary/app/api-reference/next-config-js/ppr)
at #71498.
Then also delete that from related [Partial Prerendering
docs](https://nextjs.org/docs/canary/app/api-reference/next-config-js/ppr).

### Improving Documentation

- [x] Run `pnpm prettier-fix` to fix formatting issues before opening
the PR.
- [x] Read the Docs Contribution Guide to ensure your contribution
follows the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

x-ref: docs(ppr): remove v14 mention for ppr #71498
Co-authored-by: 's avatarJJ Kasper <jj@jjsweb.site>
parent 41e401d5
...@@ -98,33 +98,6 @@ export default function Page() { ...@@ -98,33 +98,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. > - `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. > - 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. 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
```
## Dynamic Components ## Dynamic Components
When creating the prerender for your route during `next build`, Next.js requires that Dynamic APIs are wrapped with React Suspense. The `fallback` is then included in the prerender. When creating the prerender for your route during `next build`, Next.js requires that Dynamic APIs are wrapped with React Suspense. The `fallback` is then included in the prerender.
......
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