Next.js 16.2 brings 67-100% faster server Fast Refresh
Next.js 16.2 Turbopack brings Server Fast Refresh to Node.js, cutting reload times 67-100% and compile times 400-900%. Only changed modules reload, not whole chains. WASM Workers, SRI, and dynamic import tree shaking land; upgrade to cut dev latency.
Why it matters
Development speed directly shapes shipping velocity. When server-side hot reloads blast away the entire require cache including untouched node_modules, engineers wait dozens or hundreds of milliseconds for every small change. Next.js 16.2 eliminates that waste by bringing browser-style Fast Refresh to Node.js server code through Turbopack. In production-grade applications, server reload times drop 67-100% and compile times fall 400-900%, scaling from small starters to large sites like vercel.com. For teams running substantial Next.js codebases, this removes a daily friction point that compounds across every edit and test cycle.
What changed
Turbopack now uses its internal module graph to surgically reload only the module that changed, leaving the rest of the server process intact. This replaces the previous behavior of clearing require.cache for the changed file and every module in its import chain. The release also corrects Web Worker origins so they point to the application domain instead of an empty blob URL, unblocking WASM libraries that rely on relative fetch or importScripts inside Workers. Subresource Integrity is now supported as an experimental alternative to nonce-based CSP, computing script hashes at build time so pages can remain static while enforcing execution policies. Dynamic imports are now tree-shaken the same way static imports are, so unused exports inside dynamically imported modules are removed from the bundle. Developers can also configure loaders per-import using import attributes rather than global turbopack.rules, and experimental Lightning CSS configuration options are available alongside postcss.config.ts support and log filtering.
What to watch
Proxy and Route Handlers still use the legacy reload system, with Fast Refresh support planned for a future release. The team is also targeting faster compiler performance and lower memory usage in upcoming versions. If you rely on Workers for heavy compute or WASM, verify your libraries now work without origin workarounds. Turn on experimental SRI if you currently use nonces and want to move pages back to static generation. With over two hundred bug fixes and performance changes in this release, upgrading should be low risk and immediately improve local iteration speed.
Interview question
How does Turbopack's Server Fast Refresh in Next.js 16.2 differ from the previous server-side reload behavior?
- a.It clears require.cache for changed files while preserving untouched node_modules, cutting overhead by about two-thirds.
- b.It applies tree-shaking to dynamic imports during reload so that only used exports are invalidated instead of the full module graph.
- c.It reloads only the changed module and leaves the rest of the server process intact, rather than clearing the require.cache for the entire import chain.Correct
- d.It moves server compilation into Web Workers with corrected origins to isolate changes from the main Node.js process.
Why? this is the answer
Turbopack now surgically reloads only the changed module while leaving the server process intact, replacing the old behavior of clearing require.cache for the changed file and its entire import chain. Option A is tempting because it mentions require.cache and node_modules, but the old system actually cleared untouched node_modules in the import chain, and the new approach avoids chain-wide cache clearing entirely.
Just read this? Test yourself on what you have been reading.
Read the original → nextjs.org
- #next.js
- #turbopack
- #javascript
- #frontend
- #react
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on next.js — each one lists the topics its interview covers.
See open roles