next-cache-components

Partial Prerendering (PPR) in Next.js 16 allows mixing static and dynamic content in a single route. Enable it by turning on `cacheComponents` in `next.config.ts` and using the `use cache` directive for async data.

The `use cache` directive replaces `unstable_cache` in Next.js 16 by offering granular control through advanced directives like `cacheLife` and `cacheTag`. This provides explicit cache boundaries and better revalidation strategies for async functions.

The `cacheLife` directive defines the duration a cached response persists, while `cacheTag` assigns labels to cached data for targeted revalidation. They work together with the `use cache` directive to manage Next.js 16 cache expiration and on-demand purging.

Yes, the `use cache` directive and advanced caching directives like `cacheLife` and `cacheTag` require Next.js 16. You also need to enable `cacheComponents` in `next.config.ts` to activate these advanced caching capabilities.

Migrate from `unstable_cache` by adopting the `use cache` directive in your async functions and replacing configuration objects with `cacheLife` for duration and `cacheTag` for identification. This aligns your caching strategy with Next.js 16 PPR standards.