Turbopack Error: Next.js package not found

[vinay-blink]

Turbopack version: v15.5.5-2-g92bbbb1be
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

[Arjun-M]

Hey @vinay-blink 👋

This specific Turbopack crash (Next.js package not found → get_next_package failed) almost always means Turbopack can’t find your next package in node_modules. It hits this when node_modules/.bin/next is missing or the next dep is broken/malformed.

Happens a lot with:

• pnpm (hard links confuse Turbopack sometimes)
• monorepos where next isn’t hoisted
• corrupted node_modules after a bad install
• next listed in devDependencies but not dependencies in some setups

Quick fixes (try in order):

# 1. Just nuke and reinstall
rm -rf node_modules .next
npm install   # or yarn / pnpm / whatever you use

# 2. If you’re on pnpm, force hoisting for next
# add to .npmrc
node-linker=hoisted

# or just temporarily switch to npm/yarn for next@canary/turbopack

I’ve seen this exact stack trace probably 20+ times in the last couple months and 99% of the time it’s fixed by a clean install.

If that doesn’t do it, drop your package.json and lockfile name (package-lock/yarn/pnpm-lock) here and I’ll tell you exactly what’s up.

Works after the reinstall? 🚀