Turbopack had an annoying habit: every server restart meant starting cold. The build graph lived only in memory, and that memory vanished the moment you shut down the dev server. Next.js 16.3 fixes that with a persistent build cache that writes the work to disk and picks up where it left off after a restart. What used to be a cold start is now a warm one.
Built knowledge that survives a restart
Storing the cache in memory was simple but shortsighted. Turbopack now writes the build graph to disk, so a restart is no longer a blank slate — only modules that actually changed get reprocessed. For large codebases — hundreds of components, deep dependency trees — that means significant time saved on every cold start. Multiple times a day. Day after day.
Less memory, faster transforms
16.3 also ships memory eviction: Turbopack actively drops module records it no longer needs. Dev servers that used to grow unbounded as the day went on now stay lean — a roughly 90 percent reduction in peak memory use is not an edge case. On top of that, the React Compiler now runs as a Rust plugin inside Turbopack, meaning all transforms happen in the same optimised stack instead of crossing a process boundary.
Our take
Build tooling is the infrastructure you never notice when it works and always feel when it doesn't. A cache that survives restarts, a dev server that doesn't balloon across the day — these are improvements without a feature page that still pay back every single session. If you're running Next.js, 16.3 is worth picking up quickly.



