Next Js Daily: Turbopack Cache Hardening and Upgrade Split

Turbopack reliability dominated the week, with garbage collection fixes and enablement by default plus a Pages Router chunking fix. The upgrade workflow also moved toward a standalone package with rebuilt agent evals.

Duration: PT2M22S

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-10-10T22:01:01Z
  • Audio duration: PT2M22S

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 October 10th, 2026.

Our lead story: Turbopack's persistent cache just got both more aggressive and more reliable, with garbage collection turned on by default on canary after two crash fixes and a related Pages Router hydration fix.

First theme is cache correctness. Pull request 99902 fixes two garbage collection paths that left half-removed dependency edges, which triggered a panic about a missing task when collection and persistent caching were both enabled. One case involved an interrupted collection pass combined with eviction. The other…

Closely related is Pages Router development. Pull request 98823 chains the application shell and the current page into the same client module graph, so shared modules are not dropped. Pull request 99910 adds regression coverage for that failure, where hydration broke with a module factory not available error.

Second, the upgrade workflow is becoming independent. A stack led by pull requests 99880, 99973 and 99979 moves upgrade logic into its own package with a standalone upgrade command, separates Next framework integrations like config and telemetry, and rebuilds evaluation around delivered apps using Codex and Claude,…

Finally…

Nearby episodes from Next Js Daily

  1. Durable Cache Correctness and Turbopack Speedups
  2. Agent Upgrade Controls and Validator Fixes
  3. Turbopack Chunking Groundwork and Release Simplification
  4. Durable Cache Stability and Upgrade Decoupling
  5. Turbopack Trace Diet and Release Cleanup
  6. Static Guides Surge as Auth APIs Roll Back
  7. Auth APIs Go Stable and Cache Errors Get Clearer
  8. Refresh Correctness and Static Route Hardening