Turbopack Error: Failed to write app endpoint /(user)/requests/new/page

[ysrn87]

Turbopack version: ea1df5f2
Next.js version: 0.0.0

Error message:

Failed to write app endpoint /(user)/requests/new/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 /(user)/requests/new/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

[ibrahimpelumi6142]

This error indicates that Turbopack cannot resolve the next package from the directory where next dev is executed.
The Next.js version: 0.0.0 output confirms that Next.js is not being detected at all.

This is not related to the app route — that route is just the first one Turbopack tried to compile.

Quick diagnostic

Run this from the same directory you start next dev:

node -p "require.resolve('next/package.json')"

If it throws, Next.js is not resolvable from that folder.

Solutions (try in order)

1. Reinstall dependencies

rm -rf node_modules .next package-lock.json
npm install

2. Verify Next.js is listed in the app’s package.json

{
  "dependencies": {
    "next": "^14 || ^15",
    "react": "^18",
    "react-dom": "^18"
  }
}

3. Monorepo/workspace setups
   Ensure next is resolvable from the app package itself (not only the repo root).

4. Disable Turbopack (workaround)

npx next dev --no-turbo

If this works, it confirms a Turbopack resolution/caching issue.

5. Ensure Node.js version is supported (18.17+)

This matches a known Turbopack resolver issue in certain configurations.

[nextjs-bot]

This discussion appears to be a duplicate of #87816.

Please follow the discussion there: #87816

---

This comment was added automatically by discussion consolidation tool. If you believe this is in error, feel free to re-open the discussion.