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 prerendered content, cached components with 'use cache', and dynamic content wrapped in Suspense.

Replace unstable_cache wrappers with a function containing the 'use cache' directive. Move options.tags to cacheTag() calls and options.revalidate to 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 forbidden inside use cache because cached output must be request-independent. Extract the value outside the cached function and pass it as an argument, or use 'use cache: private' when compliance requirements prevent refactoring.

updateTag invalidates a cache tag immediately so the same request sees fresh data, while revalidateTag triggers background stale-while-revalidate so the next request gets updated content. 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 once at build time, so use connection() for request-time randomness.