Turbopack Error: Failed to write app endpoint /page

[spottiesolutions]

Turbopack version: v15.5.2-3-gdb56d7759
Next.js version: 0.0.0

Error message:

Failed to write app endpoint /page

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: 2147483652 } transient failed
- 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 /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]/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

[DanielSalazarLoaiza]

This error typically indicates that Turbopack failed while processing or transforming your CSS during build.
It’s often caused by an unexpected PostCSS crash or a corrupted file read when spawning a new worker process (especially on Windows).

Try deleting .next and node_modules, reinstalling dependencies, and running again. If it persists, temporarily disable custom PostCSS plugins or check if your globals.css includes invalid imports.

You can also try running with --no-turbo to confirm if it’s specific to Turbopack.