Next.js: Caching Gets Honest About What's Stale

A cluster of fixes closed gaps where cached content silently served stale or incorrect data in both dev and production, while Turbopack landed two separate memory-reduction changes to source maps and file handling. Andrew Clark also introduced granular prefetch controls to keep ISR and runtime prefetching costs predictable.

Duration: PT2M34S

Episode overview

This episode is a short developer briefing from Next.js.

It explains recent repository work in plain language.

  • Show: Next.js
  • Published: 2026-07-23T13:11:33Z
  • Audio duration: PT2M34S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

It's July 23rd, 2026, and today's developer briefing centers on one theme: caches lying to you, and the team closing those gaps.

The biggest cluster comes from unstubbable and Hendrik Liebau, fixing a chain of dev-mode `use cache` bugs. PR ninety-six-oh-twenty-two found that stale cache invalidation relied on a cookie the browser's HMR client set — which meant a plain fetch, a curl request, or a fresh browser profile never got that cookie,…

On the production side, Josh Story's PR ninety-five-eight-seventy-two and Janka Uryga's ninety-five-six-sixty-five both fix cache-key mismatches in Cache Components — one where prerenders leaked extra route params they shouldn't have, another where App Shell prerenders missed hanging inputs and caused cache misses…

Second theme: Turbopack memory. Dan Abramov's PR ninety-five-nine-three-four stops duplicating source file text across every serialized source map, cutting peak dev memory usage by roughly fifteen to twenty percent in measured apps. Separately, Benjamin Woodruff split up an oversized file-system module for…

Third, Andrew Clark is building cost controls around prefetching. PR ninety-six-oh-seventy-four gates an ISR upgrade behavior…

What…

Nearby episodes from Next.js

  1. Security Patch Wave and Windows Path Fixes
  2. Taming Instant Validation, and Turbopack's Tree-Shaking Push
  3. Chasing Down Dev Server Memory and Source Map Costs
  4. Weekly Recap - Navigation Stability & Turbopack Runtime Slimming
  5. Trimming Waste in Rendering and Requests
  6. Turbopack Performance Push and Navigation Reliability Fixes
  7. Navigation Internals Under Pressure
  8. Turbopack Runtime Overhaul and TypeScript 7 Crash Fixes