next-cache-components

You can cache Next.js components using the use cache directive at the file, component, or function level to control rendering and revalidation, effectively reducing server load while balancing static and dynamic content.

Tag-based cache invalidation in Next.js uses cacheTag to label cached data and updateTag to trigger immediate or background revalidation, ensuring precise control over cached route freshness.

Migrate from unstable_cache to use cache by replacing existing wrapper functions with the use cache directive and adopting cacheLife and cacheTag for granular revalidation control within Next.js 16 Cache Components.

Next.js Cache Components allow combining static prerendered content, cached content revalidated on request, and dynamic Suspense-based content within a single page by applying the use cache directive.

Configure cacheLife alongside the use cache directive to define specific revalidation durations for cached Next.js components, controlling exactly when background or on-request content refreshes occur.

Yes, you must enable cache components in your Next.js configuration file before applying the use cache directive and utilizing related invalidation APIs like cacheTag and updateTag in your application routes.