Next.js 16.3 cuts long dev sessions’ memory use by up to 90%
cramforce · x · 2026-08-04
Next.js 16.3 cuts long dev-session memory use by up to 90%
The Next.js team says Turbopack’s latest stable release focuses on compiler performance, especially reducing CPU and memory pressure in large apps.
- Long-running dev sessions can now use up to 90% less memory.
- The change comes from disk caching and memory eviction on by default.
- The release also adds a persistent filesystem cache for faster builds, experimental Rust React Compiler support, import.meta.glob support, and faster HMR/dev startup.
- Next.js says the memory win matters because coding agents, IDEs, typecheckers, and linters all compete for RAM during development.
- Their example after compiling 50 routes shows memory dropping from 21.5 GB to 2 GB on Vercel’s dashboard, and from 4.6 GB to 840 MB on nextjs.org.
Related event: Next.js 16.3 Cuts Dev Memory by 90% and Adds AI Docs(2 posts)→
More from coding & agent
- Eve pushes enterprise agents toward one customizable assistant per company — aarthir · 2026-08-04
- Enkstein open-sources a local control plane for Codex, Claude, Gemini, and Ollama — wcoreiron · 2026-08-04
- Gemini Spark can connect MCP servers, but every tool still needs repeated approval — tristanbob · 2026-08-04
- Agent apps should expose a skill surface, then crystallize it into code — burny_tech · 2026-08-04
- Use subagents to switch models inside one session — dotey · 2026-08-04
- xAI updates Grok Build with Grok 4.5, skills, MCP, and plan mode — elonmusk · 2026-08-04