Next.js Daily: App Router Resume Fixes and Strict Matching
App Router prerendering got more reliable with structural server keys and cleaner build-time errors, while strict route matching is now on by default. Agentic upgrades and a prefetch-loop fix round out a correctness-focused day.
Duration: PT2M14S
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-22T06:09:32Z
- Audio duration: PT2M14S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Hello and welcome to Next.js Daily for Tuesday, September 22nd, 2026.
The big signal today is App Router correctness — how prerenders resume, how invalid routes are caught at build time, and how the client handles wrong predictions.
First, server rendering and build-time generation were refactored for reliability. In PR 98944, Next.js now uses structural React keys during server rendering, so an HTML prerender for a route like products slash slug can resume for products slash shoe without rewriting React's postponed state. Browser keys and…
Second, strict route matching is now the default, in PR 97397. URLs that can't build a complete route tree are rejected, unreachable parallel-route pages are reported, and incomplete catch-all matchers are pruned. If you relied on soft navigation preserving stale slot state, your build will now warn and point to a…
Third, the AI upgrade workflow is maturing for dogfooders. PR 98870 makes the AI upgrade resolve the latest official canary instead of reusing a stale cached one, and PR 99001 enables that workflow on canary with shared eligibility checks and security reminders in dev tools.
One critical client fix to know: PR 98998 stops an infinite…
Nearby episodes from Next.js Daily
- Weekly Recap - Routing Correctness, Agent Workflows and Turbopack Efficiency
- Router Cache Refactor and Closed-Route Fix
- Router Cache Correctness and Turbopack CSS Fix
- Roots, Rendering, and Reliability
- Agentic Upgrades and Cache Correctness
- A Rocky Revert and a Turbopack Performance Push
- Routing Edge Cases and the Deploy Test Cleanup
- Turbopack Tightens Up, Agents Get Guardrails