Turbopack Error: failed to receive message

[KarunyaReddyJ]

Turbopack version: 3e37bb42
Next.js version: 0.0.0

Error message:

failed to receive message

Caused by:
- reading packet length
- An existing connection was forcibly closed by the remote host. (os error 10054)

Debug info:
- Execution of get_all_written_entrypoints_with_issues_operation failed
- Execution of PlainIssue::from_issue failed
- Execution of PlainSource::from_source failed
- Execution of <WebpackLoadersProcessedAsset as Asset>::content failed
- Execution of WebpackLoadersProcessedAsset::process failed
- Execution of evaluate_webpack_loader failed
- failed to receive message
- reading packet length
- An existing connection was forcibly closed by the remote host. (os error 10054)

[PrashantJaybhaye]

Hi @KarunyaReddyJ, this os error 10054 (Connection forcibly closed by the remote host) usually occurs when the Turbopack development server loses its connection to an internal worker process that has crashed.

Here are a few steps that often resolve this for Next.js users:

1. Clear the Build Cache 🧹

The most frequent cause is a corrupt .next or node_modules folder.

• Stop your development server.
• Delete the .next folder in your project root.
• (Optional but recommended) Delete node_modules and your lock file (e.g., package-lock.json).
• Reinstall dependencies: npm install (or your equivalent).
• Restart with next dev --turbopack.

2. Check Node.js Architecture (Windows Users) 💻

Ensure you are using a 64-bit (x64) version of Node.js. Running a 32-bit (ia32) version can sometimes lead to crashes with native dependencies like Turbopack.

• Run node -p "process.arch" in your terminal to check.
• If it returns ia32, reinstall the 64-bit version from nodejs.org.

3. Trace the Crash (Advanced Debugging) 🔍

If the error persists, you can identify exactly what's crashing the worker by enabling trace logs. Run your dev command like this:

• For PowerShell: $env:TURBOPACK_LOG="trace"; npm run dev
• For CMD: set TURBOPACK_LOG=trace && npm run dev

Check the logs right before the "10054" error appears—it will usually point to a specific file or module causing the crash.

4. Temporary Workaround

If you need to unblock your development and don't strictly require Turbopack right now, you can switch back to the standard Webpack loader by removing the --turbopack flag from your dev script in package.json.

Hope this helps! Feel free to let me know if it resolves the issue.

[KarunyaReddyJ]

I had already tried with the temporary workaround and thought to report this turbo pack issue