Turbopack Error: Failed to write app endpoint /page

[saifulislam735]

Turbopack version: d1bd5b58
Next.js version: 0.0.0

Error message:

Failed to write app endpoint /page

Caused by:
- Next.js package not found

Debug info:
- Execution of Project::hmr_version_state failed
- Execution of Project::hmr_version failed
- Execution of VersionedContentMap::get failed
- Execution of VersionedContentMap::get_asset failed
- Execution of VersionedContentMap::compute_entry failed
- Execution of *emit_assets failed
- Execution of all_assets_from_entries_operation failed
- Execution of *all_assets_from_entries failed
- Execution of endpoint_output_assets_operation failed
- Execution of <AppEndpoint as Endpoint>::output failed
- Failed to write app endpoint /page
- Execution of AppEndpoint::output failed
- Execution of AppEndpoint::app_page_entry failed
- Execution of *get_app_page_entry failed
- Execution of AppProject::rsc_module_context failed
- Execution of *ModuleAssetContext::new failed
- Execution of *AppProject::get_rsc_transitions failed
- Execution of AppProject::ecmascript_client_reference_transition failed
- Execution of *NextEcmascriptClientReferenceTransition::new failed
- Execution of AppProject::ssr_transition failed
- Execution of *FullContextTransition::new failed
- Execution of AppProject::ssr_module_context failed
- Execution of AppProject::shared_transition failed
- Execution of *FullContextTransition::new failed
- Execution of AppProject::shared_module_context failed
- Execution of *ModuleAssetContext::new failed
- Execution of get_server_resolve_options_context failed
- Execution of get_next_server_import_map failed
- Next.js package not found

[kirbx01]

I think the Next.js version: 0.0.0 here is more likely a symptom of Turbopack failing to resolve/identify the Next.js package, rather than the project actually having Next 0.0.0.

Diagnostic Suggestion from my side

Could you try running these from the Next.js app directory?

node -e "console.log(require.resolve('next'))"
npx next --version

If require.resolve('next') succeeds and npx next --version reports the expected version, then Next itself is installed correctly and this looks more like a Turbopack resolution/cache issue.

I'd also try clearing the Turbopack/Next cache first:

rm -rf .next
npm run dev

If that doesn't fix it, a clean dependency reinstall would be the next step:

rm -rf node_modules .next
npm install
npm run dev

For workspaces/monorepos, it would also be worth checking that next is declared as a dependency of the actual application package and that there aren't conflicting lockfiles.

The key diagnostic is whether Node can resolve next successfully. If it can, I wouldn't treat 0.0.0 itself as evidence that Next is missing or actually installed at version 0.0.0.

Please revert back if the issue persists, and if it gets resolved do upvote!!