Next.js Daily: Cache Fixes and Performance Improvements

Transcript

Good morning. This is Next.js Daily for May 27th, 2026.

Andrew Clark merged a critical bugfix for incorrect search params stored in cache. The issue caused static pages to store cache entries with wrong search strings, leading to stale parameters appearing in the browser address bar. The fix changes how cache writes are keyed to match request URLs properly.

Clark also merged prefetch App Shells on the client, an experimental feature that enables instant navigation to route shells even when concrete prefetches haven't completed. This addresses high-cardinality routes where prefetching every link is impractical.

Josh Story merged improvements to notFound recovery in error pathways, re-landing previous work that handles cache components more correctly during error states. This prevents hydration issues with incomplete flight data.

The team upgraded React from version d5736f09 to 75b0945b, bringing in upstream improvements across 70 files. Tobias Koppers fixed an unsound iterator implementation in Turbopack that was causing use-after-free panics during JSON serialization.

Tim Neutkens re-applied changes to write Pages Router export files directly to server/pages, fixing i18n export issues that were creating orphan HTML files interfering with routing on deployment platforms.

Additional notable merges include Firefox refresh loop fixes for streaming pages in development mode, GitHub Actions security improvements disabling npm package manager cache, and documentation updates for ISR with Cache Components and the new next/root-params API.

What's next: The team continues expanding experimental App Shell support and refining cache behavior. Infrastructure improvements focus on build performance and CI optimization.

That's your Next.js update. We'll be back tomorrow.