Next.js: Development Caching Gets a Rethink
A cluster of fixes closes out a long-running saga around how development servers cache and restore pages in the browser, while separate work tightens up partial prefetching correctness and several routing edge cases.
Duration: PT2M41S
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-18T13:11:19Z
- Audio duration: PT2M41S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good day, and welcome to the Next.js briefing for August 18th, 2026.
The top story today is the resolution of a caching problem that's been unfolding across several releases. PR 97505, from unstubbable, stops browsers from restoring stale pages during development. The backstory matters here: development used to serve pages with "no-store," then briefly tried "no-cache" behind a flag,…
Second theme: partial prefetching correctness. Lubieowoce shipped two related fixes — PR 97469 corrects an eager-hint bug where segments without explicit prefetch config were incorrectly treated as needing a full speculative prefetch, and PR 97503 stops the router from ignoring the "is-partial" signal on complete…
Elsewhere, routing correctness got attention on multiple fronts: PR 97500 fixes App Router and Pages Router locale matching in hybrid i18n setups, PR 97491 stops a Pages Router sitemap file from being misclassified as App Router metadata, and PR 97474 fixes a case where middleware errors combined with compression…
On infrastructure, two separate turbopack performance pull requests — 97475 and 97473 — both target skipping ignored files during server tracing, suggesting parallel work converging…
L…
Nearby episodes from Next.js
- 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 Comes Full Circle
- 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
- Routing Internals Get a Deep Cleanup