Next.js: Closing the Gaps in Cache Components
A cluster of fixes tightens correctness around Cache Components edge cases and Turbopack concurrency, while a Turbopack deadlock fix and a compiler safety correction round out the reliability work for August 9th.
Duration: PT2M33S
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-09T13:08:11Z
- Audio duration: PT2M33S
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 9th, and here's what moved in the Next.js codebase.
The dominant story today is Cache Components hardening. David Ilie opened a run of PRs closing behavioral gaps: PR ninety-six thousand nine eighty-seven brings back support for dynamic params set to false when Cache Components is enabled, PR ninety-six thousand nine seventy-nine stops app route prerenders as soon as…
Second theme: server action redirects across workers. PR ninety-six thousand nine seventy-seven is a direct follow-up to a prior fix, this time preserving the original host on the second internal self-fetch used for streaming action redirects. It's a narrow but important correctness fix for multi-worker deployments.
Third, Turbopack got two reliability fixes worth remembering. Luke Sandberg's PR ninety-five thousand six ninety-five fixes a real deadlock in the scope-and-block primitive — previously, jobs assigned exclusively to spawned workers could stall forever if the runtime had fewer threads than the host CPU count. The fix…
Smaller but notable: image optimizer errors now include the upstream HTTP status for clearer diagnostics, and dev validation workers stay alive across hot reloads so…
Wha…
Nearby episodes from Next.js
- Request State Gets Untangled
- Routing Loops and the PPR Cleanup
- Turbopack Rollbacks and WebSocket Route Handlers Take Shape
- Weekly Recap - Turbopack Hardening and the Render Pipeline Split
- Server Actions Get Rerouted, Request Insights Takes Shape
- Rebuilding the Router's Data Format, and a New Observability Layer
- Dev Server State Gets One Source of Truth
- App Render Gets Untangled, Turbopack Gets Hardened