Next Js Daily: A Bumpy Day for App Router Routing
A routing fix for hybrid App Router and Pages i18n projects was merged, reverted, and re-applied within hours after a stale merge broke canary, while Turbopack saw a cluster of correctness fixes around module graphs, task lifecycle, and bundling internals.
Duration: PT2M25S
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-09-16T22:00:29Z
- Audio duration: PT2M25S
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 September 16th, and here's your Next JS Daily briefing.
The headline today is release risk around routing. Tim Neutkens merged PR ninety-eight thousand ninety-five to fix App Router locale matching in hybrid Pages-i18n projects, closing out a long-standing issue. But a stale merge broke canary, triggering an immediate revert in PR ninety-eight seven fifteen, followed by…
Second theme: Turbopack's internals got several targeted correctness and safety fixes. Sokra's PR ninety-eight six sixty-one fixed import tracing so cyclic module graphs no longer panic when an entry point sits inside a cycle — instead of crashing, it now falls back to a minimal trace. Related to that, two PRs —…
Third theme: caching correctness. Aryabyte's PR ninety-eight six seventy-four, echoed by unstubbable's companion PR ninety-eight seven eighteen, fixes a real bug where a "use cache" segment reading a root param didn't invalidate correctly after client-side navigation — meaning users could see stale locale content…
Smaller but notable: mischnic's fix in PR ninety-eight seven seventeen resolves a confusing Turbopack error that masked a real server-action mistake in client components.
What's…
Nearby episodes from Next Js Daily
- Router Correctness and the Deploy Test Backlog
- Turbopack Tightens Up Its Output
- Turbopack's Task Engine Gets a Tune-Up
- Turbopack Gets Its House in Order
- The Cache Reliability Push
- Route Matching Gets Strict, and Turbopack Gets Leaner
- Clearing the Deployment Test Backlog and Caching Correctness
- Prefetch Correctness and the Great Turbopack Rebuild