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, and dynamic Suspense boundaries.

Add 'use cache' at the top of an async function, component, or file, then optionally call cacheLife for lifetime profiles and cacheTag for invalidation labels. Cache keys are generated automatically from arguments and closure variables.

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

Runtime APIs like cookies(), headers(), and searchParams are disallowed 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' 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-writes scenarios in Server Actions.

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