Turbopack Error: Failed to write app endpoint /page

[rizkiramadhanw234-bit]

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

[pouriya73]

Hi @rizkiramadhanw234-bit

This error is simple: Turbopack can’t resolve the next package from the project it’s building, so it fails when writing the /page endpoint.

1. next is not installed where you’re running the dev server

Check your package.json in the folder where you run npm run dev:

It must include "next" in dependencies (or devDependencies).

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

If that throws, Turbopack is right: Next isn’t resolvable.

npm i next react react-dom

2. You’re running next dev from the wrong directory (common in monorepos)

If you have a monorepo like:

/repo
  /apps/web   <-- next app lives here
  /packages/...

Run from the app folder:

cd apps/web
npm run dev

3. Workspace / pnpm hoisting issue (Turbopack is stricter)

If you use pnpm or workspaces, next might be installed but not visible the way Turbopack expects.

Ensure next is a dependency of the app itself (not only the root).

Reinstall clean:

rm -rf node_modules .next
pnpm install
pnpm dev

If you’re on pnpm and using isolated node-linker, try:

pnpm config set node-linker hoisted
pnpm install

4. Corrupted install / lockfile mismatch

This happens a lot when switching package managers (npm ↔ yarn ↔ pnpm).

Fix (pick your package manager and stick to it)

rm -rf node_modules .next package-lock.json yarn.lock pnpm-lock.yaml
npm install
npm run dev

5. Next binary is coming from somewhere else

If Next.js version: 0.0.0 shows up, you might be running a weird build or the wrong next is being picked up.

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

[wbinnssmith]

This discussion appears to be a duplicate of #87816.

Please follow the discussion there: #87816

---

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