next-cache-components

Partial prerendering in Next.js 16 mixes static and dynamic content in a single route to balance fast initial loads with fresh data. It splits the UI so static parts load instantly while dynamic sections stream in.

Migrate from unstable_cache to Next.js 16 cache components by replacing the legacy API with the new use cache directive, cacheLife, and cacheTag. This provides fine-grained caching controls for individual components and data fetching functions.

Yes, use cache supports dynamic routes by allowing you to mix hourly cached stats with real-time user notification streams. You can apply cacheLife and updateTag to define custom cache behavior without manual cache key management.

Invalidate cached data in Next.js 16 components by using the cacheTag and updateTag APIs. These fine-grained caching controls let you tag specific components or data fetching functions and selectively invalidate them when underlying data changes.

No, Next.js 16 replaces the old experimental.ppr flag with the new Cache Components system. You migrate away from the experimental flag to use the use cache directive for implementing partial prerendering and fine-grained caching.

Avoid using the use cache directive when your component requires strictly real-time data without any acceptable staleness, as the caching lifecycle introduces delays. It is designed for mixed static and dynamic content where reducing server load is prioritized over instant freshness.