Turbopack Error: Failed to write app endpoint /page

[TBNRGarret]

Turbopack version: da605e0c
Next.js version: 0.0.0

Error message:

Failed to write app endpoint /page

Caused by:
- [project]/src/app/globals.css [app-client] (css)
- failed to write to D:\pawtopia-ver2\.next\dev\build\chunks\[turbopack-node]_transforms_postcss_ts_6920245c._.js
- Insufficient system resources exist to complete the requested service. (os error 1450)

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 /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
- Execution of get_evaluate_pool failed
- failed to write to D:\pawtopia-ver2\.next\dev\build\chunks\[turbopack-node]_transforms_postcss_ts_6920245c._.js
- Insufficient system resources exist to complete the requested service. (os error 1450)

[aayush-dev01]

1. What the error indicates

This points to a Windows filesystem or resource limitation, not application code.
The key signal is:

Insufficient system resources exist to complete the requested service (os error 1450)

---

2. Clear caches and rebuild

rm -rf .next node_modules
npm install
npm run dev --turbo

Corrupted or partially written Turbopack artifacts commonly trigger this.

---

3. Check system resources (Windows)

• Ensure sufficient free disk space on the project drive
• Restart the system to clear stale file handles
• Close heavy background processes (IDEs, browsers, antivirus scans)

Windows is more prone to hitting file-handle limits during large builds.

---

4. Reduce path and filesystem complexity

• Move the project to a shorter path (e.g. C:\projects\app)
• Avoid deeply nested directories
• Exclude the project directory from antivirus scanning if possible

Long paths + many writes can cause Turbopack write failures on Windows.

---

5. Isolate Turbopack

npm run dev

If this works without --turbo, it strongly suggests a Turbopack-specific Windows issue.
A minimal reproduction repo plus system details would help maintainers investigate.