Next.js 16.3 cuts dev memory use ninety percent

Summary

Faster local iteration and CI builds reduce friction on large codebases; prefetch caching without abandoning server-driven rendering closes the perceived performance gap that drove teams toward SPAs.

Why it matters

Faster local iteration and CI builds reduce friction on large codebases; prefetch caching without abandoning server-driven rendering closes the perceived performance gap that drove teams toward SPAs.

Sources

1. 1.Turbopack now uses up to 90 percent less memory during next dev
2. 2.Vercel reports its own dashboard falling from 21.5GB to 2GB
3. 3.repeat builds up to 5.5 times faster on CI
4. 4.handles up to 22 percent more requests under load with no code changes
5. 5.Partial Prefetching bundles smaller prefetches into one reusable shell per route