Next.js: Garbage Collection Groundwork Lands in Turbopack's Storage Layer

Three related pull requests from Luke Sandberg build out delete and tombstone support across Turbopack's persistence and task backend, laying the plumbing for upcoming garbage collection, while a scattering of fixes addressed metadata rendering, middleware redirects, and CI reliability.

Duration: PT2M40S

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-17T13:10:09Z
  • Audio duration: PT2M40S

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 17th, and today's Next.js activity centers on one big infrastructure push, with a handful of smaller reliability fixes rounding things out.

The headline theme is garbage collection support landing in Turbopack's storage internals. Three connected pull requests from Luke Sandberg build this out layer by layer. PR 96929 adds tombstone support directly into the persistence layer, letting the database delete key-value pairs out of multi-value tables for the…

A second theme is correctness fixes around request handling and rendering consistency. PR 97255 fixes a subtle bug where Next's async local storages could be instantiated more than once per realm if a package was reachable through multiple import paths — anchoring them to global symbols instead of relying on module…

On the reliability side, gnoff's PR 97421 deflakes a cache test by polling for freshness instead of using fixed delays, and PR 97447 adds watchdog logging to catch stalled test files after a prior CI timeout.

What to remember: the tombstone and task-existence work is foundational, not user-facing yet — expect garbage collection itself in a future release. In the meantime, the async storage and…

Tha…

Nearby episodes from Next.js

  1. Module Federation Lands in Turbopack, Partial Prefetching Gains New APIs
  2. Cleaning Up Test Debt and Prefetch Bugs
  3. Development Caching Comes Full Circle
  4. Development Caching Gets a Rethink
  5. Weekly Recap - Stabilizing 16.3 and Untangling the Router
  6. Route Matching Gets Stricter, Router Gets Reorganized
  7. Routing Internals Get a Deep Cleanup
  8. Stabilizing 16.3 and Unifying the Router's Data Format