Next.js: Turbopack Memory Cuts and Dev Reliability
A stacked set of Turbopack changes slashes end-of-build memory from ~13 gigabytes to ~1 gigabyte and speeds warm compiles ~30%. Dev server handling also gets more reliable with clean errors for nested catch-all routes and signal kills.
Duration: PT2M42S
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-11-13T14:11:30Z
- Audio duration: PT2M42S
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 November 13th, 2026, you're listening to your Next.js briefing.
The throughline is scale and stability: Turbopack now holds far less memory at the end of large builds, and the dev server fails louder and cleaner when routing or processes go wrong.
First, build memory. Three stacked changes tackle shutdown memory, in PRs 101529, 101589 and 101623. Until now the main build process held twelve to thirteen gigabytes after shutdown for several seconds before dropping. By purging eagerly during persistence and then releasing small fragmented ranges back to the…
Related performance work cuts wasted recomputation. PR 101514 parallelizes effect capture across up to eight workers, cutting warm compile time about thirty percent, from roughly nine and a half seconds to six and a half in testing. And PRs 101626 and 101725 read unused reference data by key, so a change in one…
Second, dev-server reliability. PR 101697 stops a crash when a metadata file or page is nested inside a catch-all segment, reporting a normal recoverable structure error instead of aborting dev. PR 101752 makes unexpected server deaths visible, logging the signal and exiting with standard…
Finally,…
Nearby episodes from Next.js
- Turbopack Scaling Push and Prerender Fixes
- Cache Determinism Push and Rendering Fixes
- Turbopack Test Overhaul and Router Fixes
- Route Handler Speedups and RSC Revalidation Fix
- Weekly Recap - Cache Components Clarity and Turbopack Efficiency
- Cache Reliability, Memory Pressure, and Image Security
- Leaner Server Startup and Turbopack Reliability
- Request Insights Matures and Route Compression Fixed