Turbopack Error: Failed to write app endpoint /roles/project-officer/page

[Sahil-769]

Turbopack version: a9a1cb78
Next.js version: 0.0.0

Error message:

Failed to write app endpoint /roles/project-officer/page

Caused by:
- the chunking context (unknown) does not support external modules (request: node:timers/promises)

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 /roles/project-officer/page
- Execution of *all_asset_paths failed
- Execution of *AppEndpointOutput::output_assets failed
- Execution of AppEndpoint::output failed
- Execution of get_app_client_references_chunks failed
- Execution of *ChunkGroupResult::concatenate failed
- Execution of <BrowserChunkingContext as ChunkingContext>::chunk_group failed
- Execution of make_chunks failed
- Execution of batch_chunk_items_with_info failed
- Execution of batch_chunk_items_with_info_with_type failed
- Execution of chunk_items_with_info_with_type failed
- Execution of batch_size failed
- Execution of <EcmascriptChunkType as ChunkType>::chunk_item_size failed
- Execution of <EcmascriptModuleAsset as EcmascriptChunkPlaceable>::chunk_item_content failed
- Execution of *EcmascriptChunkItemContent::new failed
- Execution of EcmascriptModuleContent::new failed
- the chunking context (unknown) does not support external modules (request: node:timers/promises)

[Sahil-769]

My application was working properly, but I suddenly encountered this unexpected error and I'm unsure what caused it.

Error Type

Runtime Error

Error Message

An unexpected Turbopack error occurred. Please see the output of next dev for more details.

Next.js version: 16.3.3 (Turbopack)

[edwardsong08]

This looks like a Turbopack bundling issue rather than an application runtime error. The important part is that node:timers/promises is being pulled into the app endpoint client chunk, where that Node-only module cannot be externalized.

I would try these checks in order:

1. Remove the build output and restart dev: rm -rf .next (or delete .next on Windows), then run next dev again.
2. Search the route and its imports for node:timers/promises, including transitive server utilities. If the import is only needed on the server, move that code behind a Route Handler or Server Action and keep it out of any Client Component import chain.
3. Add import "server-only" to the server-only helper. That makes an accidental client import fail at the boundary instead of reaching the bundler.
4. Reproduce with the latest patch release and report the smallest route/import chain that still fails. The reported Turbopack commit/version is unusual, so confirming the exact Next.js package version from package.json and the lockfile will matter.

If removing the import from the client graph fixes it, the underlying problem is the server/client boundary. If it still fails with a minimal server-only route, that is a useful Turbopack regression report, and the reduced reproduction should be attached to the issue.