Next.js: Static Shell Controls and Prefetch Reliability Fixes
App Router work tightened when shells and prefetches can stay static and fixed three cases of incorrect or repeated network requests. Turbopack activity focused on watcher correctness, loader invalidation, and running core Rust tests on WebAssembly.
Duration: PT2M19S
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-09-23T13:16:08Z
- Audio duration: PT2M19S
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 23rd, 2026.
The lead pattern is control over static rendering and prefetching — the router is doing less wasted work, and developers get clearer guarantees about what stays prerendered.
First, partial prerendering now treats shells and prefetches separately. In PR 98129, runtime data tracking was split so a static shell no longer forces a static prefetch, or vice versa. PR 98191 builds on that with an ensure static option set to shell or prefetch, letting you require the shell to be statically…
Second, three reliability fixes for the client cache. PR 98998 fixes an infinite prefetch loop when a predicted route is redirected by the server — the client kept reissuing the same prefetch until the tab closed. PR 94808 stops re-requesting the app shell to upgrade an ISR fallback that is already marked retryable.…
Third, Turbopack hardening and test infrastructure. A filesystem watcher stack fixed fuzzer expectations and upgraded the notify dependency to preserve nanosecond precision, preventing missed edits in polling mode. Loader change invalidation in PR 95732 was followed by a quick fix in PR 99088 for an unknown module…
What's next: watch for the planned…
Nearby episodes from Next.js
- Turbopack Speedups, Stricter Routing, and Agent Upgrade Consolidation
- Router Cache Rework and WASI Builds
- Weekly Recap - Agents, Routing Discipline and Turbopack Efficiency
- Closed Route Prediction, Nested Dynamic CSS, and Cache Cleanup
- File Tracing Expands, Turbopack Tightens Its Bookkeeping
- Agentic Upgrades and a Turbopack Reliability Sweep
- Turbopack's Performance Push
- A Locale Fix, Two Reverts, and a Cache Bug