Turbopack Error: Failed to write app endpoint /(dashboard)/page

[dev-sweet]

Turbopack version: 23c46498
Next.js version: 0.0.0

Error message:

Failed to write app endpoint /(dashboard)/page

Caused by:
- [project]/src/app/globals.css [app-client] (css)
- failed to receive message
- reading packet length
- An existing connection was forcibly closed by the remote host. (os error 10054)

Debug info:
- Execution of get_written_endpoint_with_issues_operation failed
- Execution of endpoint_write_to_disk failed
- Execution of <AppEndpoint as Endpoint>::output failed
- Failed to write app endpoint /(dashboard)/page
- Execution of AppEndpoint::output failed
- Execution of AppProject::app_module_graphs failed
- Execution of *<AppEndpoint as Endpoint>::additional_entries failed
- Execution of *ModuleGraph::from_graphs failed
- Execution of SingleModuleGraph::new_with_entries_visited_intern failed
- [project]/src/app/globals.css [app-client] (css)
- Execution of primary_chunkable_referenced_modules failed
- Execution of <CssModuleAsset as Module>::references failed
- Execution of parse_css failed
- Execution of <PostCssTransformedAsset as Asset>::content failed
- Execution of PostCssTransformedAsset::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)

[VedantGupta19402]

The stack trace seems to point to globals.css being processed by Turbopack, but os error 10054 usually means the connection to a process was forcibly closed, so it might not be a CSS syntax issue itself.

I'd try stopping the dev server, deleting .next, and restarting it first. If it still happens, check globals.css for recent changes, especially PostCSS/Tailwind directives or imports, and try running with Webpack to see if it's Turbopack-specific.

Are you on Windows? The 10054 error makes me wonder if a process is crashing or getting interrupted while Turbopack is communicating with its CSS worker.