Turbopack Error: failed to receive message

[oleksii-lukin]

Turbopack version: d1bd5b58
Next.js version: 0.0.0

Error message:

failed to receive message

Caused by:
- reading packet length
- timeout while receiving message from process
- deadline has elapsed

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
- timeout while receiving message from process
- deadline has elapsed

Not sure if this is useful, but console told me I can report this. Running build second time without changing anything resulted in proper build failure due to typescript error I had. Not sure why first time may have failed.

> next build

▲ Next.js 16.1.1 (Turbopack)
- Environments: .env.local, .env.production

  Creating an optimized production build ...
✓ Compiled successfully in 16.3s
  Running TypeScript  ..Failed to compile.

[Thanaen]

Had a similar error.

Turbopack version: 0c06f068
Next.js version: 16.1.6

Error message:

failed to receive message

Caused by:
- reading packet length
- unexpected end of file

Debug info:
- Execution of get_written_endpoint_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
- unexpected end of file

Additional info:
I'm using Next.js with Bun. (dev script: bun --bun next dev -p 3020)
This issue doesn't occur all the time. I reported it because the CLI told me to. 😄

PS: Just deleted the .next folder, and now the issue seems to be gone.