next-cache-components-adoption

Set cacheComponents: true in next.config, then fix the blocking routes the build surfaces. The cache-components-instant-false codemod can opt every page and layout out of validation first so the build passes before you adopt routes one at a time.

Each blocking-prerender error links to a docs page at nextjs.org/docs/messages with the canonical fix recipe. Common fixes push request-time reads like cookies(), headers(), params, and searchParams into Suspense-wrapped child components.

No, Cache Components is an App Router feature and the cacheComponents flag does nothing for pages/ routes. A hybrid app works fine since the flag only affects app/ routes, but a pages-only project needs a Pages-to-App migration first.

Next.js 16.3 or later is required, since that release adds top-level cacheComponents, export const instant, dev-overlay validation warnings, and the instant-false codemod. Older versions should upgrade via npx @next/codemod@latest upgrade latest.

Sync-IO calls like new Date(), Date.now(), Math.random(), and crypto.randomUUID() fail the build even with the opt-out. Fix them with the await connection() plus Suspense pattern from the error's docs page, and check shared layouts that block every route.

Keep it when a route is genuinely per-request with no useful static shell, such as a fully request-time dashboard, or when the refactor is too large for now. Confirm with the user and replace the TODO comment with a documented reason.