next-cache-components

Set cacheComponents: true in next.config.ts to enable Cache Components, which replaces the old experimental.ppr flag. Routes can then mix static, cached, and dynamic content in a single page.

Replace unstable_cache wrappers with a function containing the 'use cache' directive, move options.tags into cacheTag() calls, and convert options.revalidate into cacheLife({ revalidate: N }). Manual keyParts arrays are no longer needed because cache keys derive automatically from arguments and closures.

Runtime APIs like cookies(), headers(), and searchParams are not allowed inside use cache because cached output must be request-independent. Extract the value outside and pass it as an argument, or use 'use cache: private' when compliance requires runtime access.

updateTag invalidates a cache tag immediately so the same request sees fresh data, while revalidateTag triggers background revalidation with stale-while-revalidate behavior. Use updateTag after mutations needing instant consistency.

No, Cache Components require the Node.js runtime and a server; Edge runtime and static export are not supported. Non-deterministic values like Math.random() inside use cache also execute only once at build time.