An unexpected Turbopack error occurred

[remcohaszing]

We’ve recently started seeing this error randomly:

$ yarn next build
   ▲ Next.js 16.0.8 (Turbopack)
   - Environments: .env.production
   - Experiments (use with caution):
     ✓ browserDebugInfoInTerminal

   Creating an optimized production build ...
FATAL: An unexpected Turbopack error occurred:
failed to receive message

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

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
- unexpected end of file

> Build error occurred
Error [TurbopackInternalError]: failed to receive message

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

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
- unexpected end of file
    at <unknown> (TurbopackInternalError: failed to receive message) {
  type: 'TurbopackInternalError',
  location: undefined
}

It was definitely occurring in Next.js 16.0.6. It could be earlier. Given recent critical updates to Next.js and (for us) next-intl, and its randomness, it’s hard to determine what could cause this.