https://github.com/vercel-labs/next-partial-prerendering

https://github.com/vercel-labs/next-partial-prerendering

nextjs vercel

Last synced: about 7 hours ago
JSON representation

• Host: GitHub
• URL: https://github.com/vercel-labs/next-partial-prerendering
• Owner: vercel-labs
• Created: 2023-11-08T03:32:53.000Z (about 1 year ago)
• Default Branch: main
• Last Pushed: 2024-10-30T15:57:01.000Z (about 2 months ago)
• Last Synced: 2024-12-17T22:02:35.618Z (7 days ago)
• Topics: nextjs, vercel
• Language: TypeScript
• Homepage: https://www.partialprerendering.com/
• Size: 1.67 MB
• Stars: 291
• Watchers: 8
• Forks: 57
• Open Issues: 4
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
## Next.js Partial Prerendering

This is a demo of [Next.js](https://nextjs.org) using [Partial Prerendering](https://nextjs.org/docs/app/api-reference/next-config-js/partial-prerendering).

This template uses the new Next.js [App Router](https://nextjs.org/docs/app). This includes support for enhanced layouts, colocation of components, tests, and styles, component-level data fetching, and more.

It also uses the experimental Partial Prerendering feature available in Next.js 14. Partial Prerendering combines ultra-quick static edge delivery with fully dynamic capabilities and we believe it has the potential to [become the default rendering model for web applications](https://vercel.com/blog/partial-prerendering-with-next-js-creating-a-new-default-rendering-model), bringing together the best of static site generation and dynamic delivery.

> ⚠️ Please note that PPR is an experimental technology that is not recommended for production. You may run into some DX issues, especially on larger code bases.

## How it works

The index route `/` uses Partial Prerendering through:

1. Enabling the experimental flag in `next.config.js`.

```js

experimental: {

    ppr: true,

},

```

2. Using `` to wrap Dynamic content.