next-cache-components

You can migrate unstable_cache to Next.js 16 by converting legacy patterns into a use cache function that defines cacheLife profiles and applies cacheTag for tagging cached outputs. This enables consistent revalidation behavior and tag-based invalidation.

Partial Prerendering (PPR) structures mixed static, cached, and dynamic content in a single route using Cache Components. It applies the use cache directive to cache async data safely while allowing dynamic parts to stream when needed.

You cannot use cookies, headers, or searchParams inside a standard use cache directive due to runtime constraints. If refactoring isn’t feasible, you should use the use cache: private directive instead to handle request-specific data safely.

The best way to invalidate cached data is to use cacheTag to label cached outputs, updateTag for immediate same-request freshness, and revalidateTag to trigger background revalidation. This tag-based invalidation ensures your server-rendered content stays consistent.

You configure cacheLife by applying the use cache directive with predefined cacheLife profiles or custom stale, revalidate, and expire settings. This reduces redundant work by safely caching async data in your App Router pages.

You should enable cacheComponents when you need to reduce redundant work in slow or over-fetching App Router pages. It allows you to apply Partial Prerendering (PPR) and cache directives so async data is cached safely while dynamic parts stream.