Turbopack Error: Next.js package not found

[tjg-iberia]

Turbopack version: db56d775
Next.js version: 0.0.0

Error message:

Turbopack Error: Next.js package not found

[DanielSalazarLoaiza]

This error typically indicates that Turbopack cannot resolve the Next.js package within the current project context. It’s often caused by incorrect project structure, missing dependencies, or internal inconsistencies between Turbopack and Next.js versions.

Technical Explanation

Turbopack attempts to locate the Next.js package using a traversal of the project’s dependency tree (starting from the working directory). If next is not found within node_modules, or if it’s installed globally or hoisted incorrectly (e.g. in monorepo setups), the resolution fails with this error.
Additionally, some early internal Turbopack builds (like db56d775) may have incomplete logic for resolving Next.js in custom or experimental setups, leading to false negatives.

Steps to Resolve

1. Verify local installation

npm ls next

If it shows (empty) or missing, reinstall it:

npm install next react react-dom

2. Ensure correct project root
   Run Turbopack or next dev --turbo from the same directory where your package.json resides.
   Incorrect working directories often cause this issue.

3. Clear caches and rebuild

rm -rf .next node_modules
npm install
npm run dev

4. Check your package manager configuration

• If you’re using pnpm, make sure node-linker=hoisted in .npmrc.

• For monorepos, ensure next is installed in the same workspace as your app (not only in the root).

5. Upgrade to a stable or canary build
   Some older Turbopack snapshots (including db56d775) are missing dependency resolution patches.

npm install next@canary

6. (Optional) Debug package resolution
   Run:

node -p "require.resolve('next')"

If this throws an error, the package truly isn’t resolvable from your current working directory.