next-cache-components

Set cacheComponents: true in your next.config file, which replaces the old experimental.ppr flag. Once enabled, routes can mix static prerendered content, use cache components, and Suspense-wrapped dynamic content.

Replace the unstable_cache wrapper with a function containing the 'use cache' directive. Move options.tags into cacheTag() calls and options.revalidate into cacheLife({ revalidate: N }); manual keyParts arrays are no longer needed since cache keys generate automatically from arguments and closures.

Runtime APIs like cookies(), headers(), and searchParams are not allowed inside use cache because cached content must be request-independent. Extract the value outside the cached function and pass it as an argument, or use the 'use cache: private' profile for compliance cases.

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 for read-your-own-writes scenarios in Server Actions.

No, Cache Components require the Node.js runtime and do not support Edge runtime or static export. Non-deterministic values like Math.random() inside use cache also execute once at build time, so use connection() for request-time randomness.