Turbopack Build Failures: OOM, Linked Packages, CSS HMR
The Turbopack failures we have hit on Next.js 16: out-of-memory builds, symlinked packages not resolving, CSS Modules not hot-reloading, loader config.
Writing
Turbopack: what we have had to fix
5 write-ups from production, newest first. Each one is a problem hit on a real project and how it was diagnosed and fixed.
Next.js 16 next start 500 Error After Turbopack Build
Next.js 16 next build passes but next start returns a 500 with Cannot find module? Turbopack quietly ignored your custom webpack config. Here is the real fix.
Next.js 16.2 Turbopack Build Out of Memory on Vercel
Next.js 16.2 Turbopack production build crashing with JavaScript heap out of memory on Vercel? Here is what changed and the build config that gets it green.
Next.js 16 Turbopack CSS Modules HMR Not Updating Fix
Next.js 16 Turbopack not picking up CSS module changes after save? Here is why HMR silently breaks for barrel imports and the workaround to ship today.
Next.js Turbopack Linked Package Reload Fix
Next.js Turbopack linked package reload issues usually come from symlink watching and package transpilation. Here is the 16.2.4 fix path I use today safely.