Turbopack Error: Failed to write page endpoint /_error

[p3droml]

Turbopack version: eac0b00d
Next.js version: 0.0.0

Error message:

Failed to write page endpoint /_error

Caused by:
- [project]/app/globals.css [app-client] (css)
- creating new process
- reading packet length
- unexpected end of file

Debug info:
- Execution of TaskId { id: 2147483650 } transient failed
- Execution of get_all_written_entrypoints_with_issues_operation failed
- Execution of EntrypointsOperation::new failed
- Execution of all_entrypoints_write_to_disk_operation failed
- Execution of Project::emit_all_output_assets failed
- Execution of *emit_assets failed
- Execution of all_assets_from_entries_operation failed
- Execution of *all_assets_from_entries failed
- Execution of output_assets_operation failed
- Execution of <PageEndpoint as Endpoint>::output failed
- Failed to write page endpoint /_error
- Execution of PageEndpoint::output failed
- Execution of PageEndpoint::client_chunks failed
- Execution of *ChunkingContext::evaluated_chunk_group failed
- Execution of Project::client_chunking_context failed
- Execution of *get_client_chunking_context failed
- Execution of Project::module_ids failed
- Execution of Project::whole_app_module_graphs failed
- Execution of whole_app_module_graph_operation failed
- Execution of *ModuleGraph::from_single_graph failed
- Execution of SingleModuleGraph::new_with_entries failed
- [project]/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
- creating new process
- reading packet length
- unexpected end of file

[PodkopovP]

Manage to find a fix?

[PodkopovP]

I managed to fix it - in my case, it was because I'm using [email protected], however in my globals.css I was doing "@import "tailwindcss";" instead of @tailwind base etc.

They need to update their their startup example as this was the defaults, however by trying to build without --turbopack I managed to get more detailed logs that led me to find this issue