Next.js: Development Caching Comes Full Circle
A multi-PR cleanup finally resolved a long-running development caching bug where stale pages resurfaced on back navigation, letting the team delete workaround code that had accumulated since spring. Meanwhile, a separate cluster of test-infrastructure PRs is stripping out native package dependencies to make the test suite faster and more reliable.
Duration: PT2M30S
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-08-19T13:12:21Z
- Audio duration: PT2M30S
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 August 19th, 2026.
The headline today is closure: a caching bug that spawned workarounds over four months finally got fixed at the root, and the team is now cleaning up the debris.
Here's the story. Development pages were served with a "no-cache" header, which sounds safe but isn't - browsers can still restore a stored document on back navigation without checking with the server, and dev documents have no ETag to validate against. So going back in your browser could show you stale code from…
That single fix made an entire subsystem unnecessary. PR 97510, right behind it, rips out the development debug channel persistence - the IndexedDB writes, the cache-restore detection, the reload fallback - all of it existed only to paper over the stale-page bug. With the root cause gone, that machinery had nothing…
Second theme: test infrastructure is getting a native-dependency diet. Eps1lon opened three related PRs - 97541, 97542, and 97543 - replacing real packages like sqlite3 with small local addon fixtures the team controls directly. The motivation is consistent across all three: pinned native packages were failing to…
Rounding out the day: gnoff's PR 97431 reworks how…
Nearby episodes from Next.js
- Tightening Up Static Rendering Edges
- Partial Prefetching Precedence Gets Cleaned Up
- Module Federation Lands in Turbopack, Partial Prefetching Gains New APIs
- Cleaning Up Test Debt and Prefetch Bugs
- Development Caching Gets a Rethink
- Garbage Collection Groundwork Lands in Turbopack's Storage Layer
- Weekly Recap - Stabilizing 16.3 and Untangling the Router
- Route Matching Gets Stricter, Router Gets Reorganized