Next.js Daily: Turbopack Gets Faster, Not-Found Routes Get Fixed

Turbopack picked up default build caching, restructured chunking config, and a napi bindings migration, while the team closed out a cluster of not-found rendering bugs affecting adapters and cache components. A new observability push is also underway, adding OpenTelemetry tracing for Server Actions and route preparation.

Duration: PT2M46S

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-08-01T06:04:40Z
  • Audio duration: PT2M46S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

Good evening. It's August 1st, and this is Next.js Daily.

Today's biggest pattern: Turbopack build performance and correctness got serious attention, while a cluster of fixes closed out edge cases in not-found route rendering.

Start with Turbopack. Sokra's PR 96395 turns on the file system cache for production builds by default, matching what dev mode already does. That's a real win for anyone running repeated builds outside CI — warm builds should get noticeably faster with no config changes needed. Alongside that, Sam Poder consolidated…

Second theme: not-found routes and adapters. Zack Tanner landed two related fixes — PR 96390 corrects build output when a statically generated not-found route is actually partially prerendered under cache components, so it no longer gets miscategorized as a complete static 404. PR 96392 handles the trickier case…

Third, a new observability push from DavidIlie: OpenTelemetry spans for Server Action execution, client component loading timing, and App Router render preparation are all landing as separate PRs — 96458, 96455, 96456, and 96453. Together they extend Request Insights with much finer-grained tracing.

Also worth noting: eps1lon consolidated…

Nearby episodes from Next.js Daily

  1. Cache Components Grows Up
  2. Partial Prerendering Gets Its Edge Cases Fixed
  3. Turbopack's HMR Overhaul and the Prefetching Reset
  4. Request Insights Gets a Foundation Rebuild
  5. Weekly Recap - Memory Leaks, Dev Server Responsiveness, and Turbopack Tree-Shaking
  6. Turbopack's Dev Server Gets Its Reliability Fixed
  7. Plugging the Long-Running Server Leaks
  8. The Long-Running Server Cleanup