Turbopack Error: Next.js package not found

[Devansh4971]

Turbopack version: 91e5b6b8
Next.js version: 0.0.0

Error message:

Next.js package not found

Debug info:
- Execution of get_entrypoints_with_issues_operation failed
- Execution of EntrypointsOperation::new failed
- Execution of Project::entrypoints failed
- Execution of AppProject::routes failed
- Execution of directory_tree_to_entrypoints_internal failed
- Execution of directory_tree_to_loader_tree failed
- Execution of get_next_package failed
- Next.js package not found

[victormoni]

Hi @Devansh4971

You’re seeing “Next.js package not found” (with Next.js version: 0.0.0) because Turbopack can’t resolve next from your project. Here’s a fast checklist that fixes it in almost all cases.

Quick fix (pick your package manager)

npm

rm -rf node_modules package-lock.json .next
npm install next react react-dom
npm run dev -- --turbo

yarn

rm -rf node_modules yarn.lock .next
yarn add next react react-dom
yarn dev --turbo

pnpm

rm -rf node_modules pnpm-lock.yaml .next
pnpm add next react react-dom
pnpm dev --turbo

Things to double-check

1. Run from the project root (the folder that has your package.json).
Running next dev --turbo in a subfolder will produce this error.

2. package.json must include:

"dependencies": {
  "next": "14.x",        // or the version you use
  "react": "18.x",
  "react-dom": "18.x"
}

(Don’t put next only in devDependencies for app runtime.)

3. Node version
Use Node >= 18.17 (or 20.x). Check with node -v. If needed, switch via nvm:

nvm install 20 && nvm use 20

4. Monorepo / workspaces (TurboRepo, Nx, etc.)

Ensure the app package (e.g., apps/web/package.json) has next in its own dependencies or is properly hoisted.

From that app’s directory, run the dev script:

pnpm --filter web dev --turbo

If using Yarn/PNPM workspaces, make sure nodeLinker/hoisting isn’t excluding next.

5. Lockfile mismatch
If the repo was installed with a different manager (e.g., pnpm-lock.yaml present), use the same tool. Mixing npm/yarn/pnpm often causes resolution failures.

6. Corrupted install
If errors persist, do a clean reinstall:

rm -rf node_modules .next
# remove the lockfile for your manager, then
corepack enable   # (for yarn/pnpm if needed)
<manager> install

7. Bun
If you installed with Bun, try running with Node once:

npm run dev -- --turbo

If it works on Node, the issue is Bun’s resolver—stick to Node for Turbopack.

[icyJoseph]

Not necessarily. This happens most often because multiple lock files are found.

@Devansh4971 you should refer to: #78192 (comment)

Also, the latest Next.js canary versions show how many lock files are found, and which one will be used.