Next.js: Stabilizing 16.3 and Unifying the Router's Data Format
A large batch of backports hardened the 16.3 release line against navigation, caching, and build regressions, while a parallel effort on canary finished unifying every router prefetch response into a single data format.
Duration: PT2M51S
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-14T13:11:42Z
- Audio duration: PT2M51S
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 14th, and today's activity is dominated by cleanup: stabilizing the 16.3 release and finishing a long-running router refactor.
The biggest signal is how many fixes are backports into next-16-3. Andrew Clark backported a race condition where pressing Back before hydration finishes could leave the page showing the wrong content, PR 97324, plus a fix for infinite prefetch loops under certain proxy and locale setups, PR 97325. Unstubbable…
Second theme: build and adapter regressions. Unstubbable and Rodrigo Arias fixed a validation bug scoping app-entry checks too broadly, breaking pages named sitemap or robots, PR 97350 and its 16.3 backport in PR 97357. Tim Neutkens fixed a missing Pages runtime dependency in adapter-built API routes, PR 96819. And…
Third theme: the router rewrite. Andrew Clark's stack, PRs 96788, 96876, 96877, and 96878, converts every RSC prefetch and navigation response to one shared format called NavigationFlightResponse. This retires several duplicated code paths and fixes inconsistencies that had accumulated across them, including one…
Worth noting separately: David Ilie's tracing work, PRs 97295 and 97296, gives Request Insights…
What's…
Nearby episodes from Next.js
- 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
- Turbopack Internals Get a Deep Cleanup
- Request State Gets Untangled
- Routing Loops and the PPR Cleanup
- Turbopack Rollbacks and WebSocket Route Handlers Take Shape