next-cache-components

To enable partial prerendering in Next.js, set `cacheComponents: true` in your `next.config.ts` file. This replaces the old experimental.ppr flag and allows Next.js routes to mix static, cached, and dynamic content.

Next.js cache components enable Partial Prerendering by mixing static, cached, and dynamic content in a single route. Static pages are prerendered at build, cached content uses `use cache` with `cacheLife`, and dynamic content loads via Suspense.

You invalidate cached content in Next.js by applying directives like `use cache`, `cacheTag`, and `updateTag`. These utilities control caching behavior and enforce safe, predictable cache invalidation patterns for your route components.

Yes, Next.js partial prerendering supports dynamic user-specific data by utilizing Suspense boundaries. This allows an instantly available static shell to load while fresh, dynamic content is fetched asynchronously.

Use `cacheLife` with `use cache` for content that should be cached and updated periodically, like hourly stats. Use Suspense for dynamic content requiring fresh data on each request, ensuring safe, predictable performance.