next-partial-prefetching-adoption

Set partialPrefetching: true in next.config alongside cacheComponents: true, after opting each destination route in with export const prefetch = 'partial'. Audit existing Link prefetch={true} navigations first so the prefetched UI users rely on is preserved.

Use the instant() helper from the @next/playwright package against a production build with experimental.exposeTestingApiInProductionBuild enabled. Run the suite with partialPrefetching disabled first to lock the legacy baseline, then rerun it after each route adopts.

Yes, both the partialPrefetching flag and the route-level prefetch export require cacheComponents: true with a passing build. It also requires Next.js 16.3 or later, where the flag, route config, and prefetch insights were introduced.

It fires in next dev when a params or searchParams read sits too high in the suspended subtree, tying the shared App Shell to one URL. Fix it by moving the read behind a deeper Suspense boundary so the shell stays shared across URLs.

The Insights tab only appears after an insight has fired, so a clean route shows no tab at all. Confirm the clean state from the dev server log, and check for blocking-prerender errors, which replace insights on their route.

Use it only when a specific link should resolve URL-specific content before the click, since each per-link prefetch costs a server invocation. Default links already prefetch the shared App Shell, so keep prefetch={true} for routes where instant URL data justifies the cost.