next-cache-components

To use partial prerendering in Next.js 16, enable cache components and apply the 'use cache' directive to mix static shells, cached data, and dynamic sections requiring fresh data within server-first routes.

Next.js cache components differentiate content into static shells that are auto-prerendered, cached data managed by the 'use cache' directive, and dynamic sections wrapped in Suspense that require fresh data.

Yes, you can migrate from older experimental.ppr implementations to Next.js 16 cache components using provided migration guidance to transition your partial prerendering setup smoothly.

The cacheLife, cacheTag, and updateTag APIs manage caching strategies within the 'use cache' directive ecosystem to control cache duration, assign tags for targeted invalidation, and force updates in Next.js 16.

Edge-case constraints when mixing cached and dynamic sections involve specific limitations on combining static, cached, and dynamic content types within a single route, which are detailed in the provided migration guidance.