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.

Replace the unstable_cache wrapper with a function containing the 'use cache' directive. Move options.tags into cacheTag() calls, convert options.revalidate into cacheLife({ revalidate: N }), and remove manual key arrays since cache keys generate 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 and pass it as an argument, or use 'use cache: private' when compliance requirements prevent refactoring.

updateTag invalidates the cache immediately so the same request sees fresh data, while revalidateTag triggers background stale-while-revalidate so the next request gets updated content. Both are called from Server Actions after a data mutation.

No. Cache Components require the Node.js runtime and a running 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.