Next.js: Turbopack's Performance Push

A cluster of merged changes targets Turbopack's memory and speed—shared AST tries, sharded persistence metadata, and dense key-block layouts—while several open PRs work through caching correctness edge cases around root parameters and nested caches.

Duration: PT2M57S

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-17T13:13:02Z
  • Audio duration: PT2M57S

Transcript excerpt

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

Good day, and welcome to the Next.js briefing for September 17th, 2026.

The clear signal today is a coordinated push to make Turbopack leaner and faster, paired with a steady stream of caching correctness fixes.

On performance: Luke Sandberg landed a series of changes to Turbopack's internals. PR 98581 replaces per-path AST storage with a shared trie, cutting peak memory on a stress repro from 24 gigabytes down to 4. PR 97703 and PR 97705 rework turbo-persistence's metadata storage—sharding by family and packing key blocks…

On correctness, especially around caching: unstubbable filed three related fixes. PR 98808 fixes metadata propagation so nested caches correctly inherit tags and lifetime before a request completes. PR 98810 extends root-parameter tracking to private caches in production, closing a gap where content could be wrongly…

Also worth noting: PR 98717 fixed a confusing Turbopack error where a valid "use client" directive was flagged as misplaced—the real problem, an inline server action in a client component, was being masked. And PR 98649 stops streaming responses that already sent a 200 status from incorrectly reporting as 500 errors…

On the content side, two…

Nearby episodes from Next.js

  1. A Locale Fix, Two Reverts, and a Cache Bug
  2. Pages Router Prefetch Bugs and Turbopack Tree Shaking
  3. Turbopack's Bundle Diet
  4. Weekly Recap - Caching Correctness and Turbopack Hardening
  5. Closing the Gaps Windows and Test Proxies Left Open
  6. Turbopack's Performance and Correctness Push
  7. Route Correctness and Cache Timing Fixes
  8. Turbopack Path Handling Gets a Real Fix