Turbopack Error: Failed to write app endpoint /page

[joychandrauday]

Turbopack version: dc98c04f
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
-

[thangsauce]

Hey joy!

That error usually means Turbopack cannot resolve the local next package for the app it is trying to run, and the Next.js version: 0.0.0 line is a strong clue that it is not seeing a normal installed Next.js dependency. GitHub discussions and issues show this exact Turbopack failure pattern, including Failed to write app endpoint /page and Next.js package not found.

Most often, one of these is the cause:

next is missing from that app’s package.json or not installed in node_modules. Next.js expects the package to be installed locally for the app.
You are in a monorepo/workspace and running the dev server from the wrong directory, so Turbopack is looking in the wrong place for next. There are open reports specifically around monorepo setups hitting Next.js package not found.
Your install is broken or partially hoisted, so the app can run inconsistently depending on workspace state or lockfile state. The official docs say module-not-found errors commonly come from missing installs or incorrect resolution.
You are on an unusual/corrupt version state, since Next.js version: 0.0.0 is not a normal released version string. Current Turbopack docs are for normal Next.js releases, and Next 16.x is the current documented line.

Do these checks in order:

npm ls next

or

pnpm why next

or

yarn why next

If that does not show a proper installed version for the app, install it in the app itself:

npm install next react react-dom

or in pnpm:

pnpm add next react react-dom

Then make sure your package.json has something like:

{
"dependencies": {
"next": "^16.0.0",
"react": "^19.0.0",
"react-dom": "^19.0.0"
}
}

Also check that you are starting the app from the correct folder:

pwd
cat package.json

If this is a monorepo, run the dev command from the actual Next app directory, not the repo root, unless your workspace script is explicitly targeting that app. Reports on GitHub show this error happening in monorepo setups when Turbopack resolves from the wrong project root.

Then do a clean reinstall:

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

If you use pnpm, the equivalent is:

rm -rf node_modules .next
pnpm install
pnpm dev

If it still fails, try without Turbopack to confirm whether this is specifically a Turbopack resolution issue:

next dev

Turbopack is built into Next.js for dev, but Turbopack-specific issues are tracked separately and this exact message appears in Turbopack reports.