Next Js Daily: Turbopack Memory Cuts and Routing Hardening

Turbopack and task storage work dominates the day, cutting over a gigabyte of peak build memory, alongside targeted routing, image security, and dev server reliability fixes.

Duration: PT2M37S

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-11-08T22:00:31Z
  • Audio duration: PT2M37S

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 Sunday, November 8th, 2026.

The lead story is efficiency inside the build engine. Multiple changes strip memory and fix correctness in Turbopack and background task storage, with measured savings of nearly a gigabyte in task storage alone.

First theme is doing more with less memory. Pull request 101344 releases unused capacity in task storage by tightening how lazy fields, aggregation edges, and empty collections hold onto space. On a large test app, total task storage dropped from about 6.5 gigabytes to about 5.6 gigabytes with no CPU regression.…

Second theme is Turbopack correctness at scale. Pull request 101387 fixes module merge order under scope hoisting, so side-effectful modules no longer run early. Pull request 101374 adds an experimental, off-by-default option to defer evaluation of side-effect-free server modules until first use. And pull request…

Third theme is routing and request hardening. Pull request 101369 closes an image security gap where a single-star hostname pattern could match across domain labels and approve an attacker host. Now a single star stays inside one label. Pull request 101390 adds base path handling to relative redirects in route…

W…

Nearby episodes from Next Js Daily

  1. Turbopack Memory Scale-Down and Prerender Fixes
  2. Order-Aware Caching and Portable Builds
  3. Turbopack Scale Push and Image Warning Fix
  4. Prerender Reliability and Turbopack Test Overhaul
  5. Cutting Per-Request Waste and Slimming Client Bundles
  6. Cache Correctness and Turbopack Cleanup
  7. Turbopack Reliability Fixes and Routing Safety Net
  8. Request Insights Lands, Turbopack Tightens Up