Unverified Commit 5fe14c42 authored by Michael Novotny's avatar Michael Novotny Committed by GitHub

[Docs] Add PPR option to `next.config.js` docs (#58161)

### Description

Adds config for experimental PPR support

### Related Issue(s)/Incident

Prior art: #57444

### Best Way to Test

Visit → docs/app/api-reference/next-config-js/partial-prerendering
Co-authored-by: 's avatarAmy Burns <5012825+timeyoutakeit@users.noreply.github.com>
Co-authored-by: 's avatarLee Robinson <9113740+leerob@users.noreply.github.com>
parent d05b817e
---
title: Partial Prerendering (experimental)
description: Learn how to enable Partial Prerendering (experimental) in Next.js 14.
---
> **Warning**: Partial Prerendering is an experimental feature and is currently **not suitable for production environments**.
Partial Prerendering is an experimental feature that allows static portions of a route to be prerendered and served from the cache with dynamic holes streamed in, all in a single HTTP request.
Partial Prerendering is available in `next@canary`:
```bash filename="Terminal"
npm install next@canary
```
You can enable Partial Prerendering by setting the experimental `ppr` flag:
```js filename="next.config.js"
/** @type {import('next').NextConfig} */
const nextConfig = {
experimental: {
ppr: true,
},
}
module.exports = nextConfig
```
> **Good to know:**
>
> - Partial Prerendering does not yet apply to client-side navigations. We are actively working on this.
> - Partial Prerendering is designed for the [Node.js runtime](/docs/app/building-your-application/rendering/edge-and-nodejs-runtimes) only. Using the subset of the Node.js runtime is not needed when you can instantly serve the static shell.
Learn more about Partial Prerendering in the [Next.js Learn course](/learn/dashboard-app/partial-prerendering).
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