Next Js Daily: Chasing Down Cache Invalidation Bugs
A cluster of fixes from developer Dan Abramov target overly aggressive cache invalidation in dev mode, while separate PRs improve dev server resilience and build performance. The common thread: making dev feedback loops trustworthy and durable.
Duration: PT2M28S
Episode overview
This episode is a short developer briefing from Next Js Daily.
It explains recent repository work in plain language.
- Show: Next Js Daily
- Published: 2026-07-26T22:00:34Z
- Audio duration: PT2M28S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning. It's July 26th, and today's activity centers on one core problem: dev servers throwing away work they shouldn't.
The headline theme is "use cache" invalidation in development. PR 96235 found that the hash keying cached entries was wrong in both directions — refreshing too often, wiping cached data on server startup or when just adding or removing a page, with no actual code changes involved. Two follow-up PRs dig deeper into…
The second theme is dev server durability. PR 96242, from Pete Hunt, fixes a real footgun: piping `next dev` into something like `head -20`, or running it in a detached tmux pane, could make the server hang permanently. Once the read end of a pipe closes, Node throws an uncaught exception on the next log write, and…
Rounding out the day: PR 96239 adds an experimental flag to run TypeScript checking concurrently with Turbopack compilation during production builds — still opt-in and Turbopack-only for now. And two infrastructure PRs, 96236 and 96234, tighten up the benchmarking pipeline — making sure stats runs use locally built…
What's next: if you rely on custom cache handlers in dev, watch for the Turbopack hash changes landing — they directly…
That…
Nearby episodes from Next Js Daily
- Plugging the Long-Running Server Leaks
- Squashing Memory Leaks and Chasing Deopts
- TypeScript 7 Fire Drill and Static Rendering Guardrails
- Dev Cache Gets an Honesty Fix
- Security Patches and Turbopack's Path Problem
- Hardening the Edges of Cache Components and Turbopack
- Chasing Down Dev Server Memory Leaks
- Duplicate Data, Duplicate Fixes