Troubleshooting
Common issues and fixes encountered during local development.
Next.js HMR Loops / Full Page Reloads
Symptom: The app keeps doing full page reloads instead of HMR (hot module replacement) updates. You'll see a pattern in DevTools like:
422e8755f9b24731.webpack.hot-update.json 200
12be9a7f109e7af1.webpack.hot-update.json 404 ← triggers full reload
signin 200 document (from hot-reloader-pages.js)
The HMR fetches are initiated by VMxxxxx (eval'd) scripts.
Root cause: The Console Ninja VS Code extension injects scripts into the browser on every page load. Those scripts attempt to open a WebSocket connection to localhost:63960. When that server isn't reachable, the injected script keeps retrying, interfering with Next.js HMR — causing a loop where a *.webpack.hot-update.json request returns 404, which triggers a full reload, and the cycle repeats.
Fix: Disable the Console Ninja extension in VS Code and hard refresh the browser.
Tip
If you install Console Ninja to improve your debugging experience and suddenly see weird hot-reload behavior, this is likely the culprit. Disable the extension first before investigating further.
All-White Screen with __turbopack_load_page_chunks__ is not defined
Symptom: Running bun run dev shows an all-white screen with this error in the browser console:
Uncaught ReferenceError: __turbopack_load_page_chunks__ is not defined
Root cause: A Turbopack bug where its internal cache gets corrupted (related to a Rust-level CLOEXEC pipe assertion failure). This is not caused by any code changes — it's a bug in the bundler itself.
Fix:
- Stop the dev server
- Clear the Next.js cache:
rm -rf apps/web-commercial/.next - Run
bun run devagain - Hard refresh the browser with
Cmd+Shift+R
If it happens again after that, also clear the Turbo cache:
rm -rf node_modules/.cache .turbo apps/web-commercial/.next
Note
This only affects local development. Production and staging builds on Vercel are not impacted since they always do clean builds.