Turbopack Error: Next.js package not found

[AkbarAlam]

Turbopack version: v15.3.0-canary.45-23-g664110c18

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

[hqw567]

In a Turborepo-powered monorepo, running the Next.js app with Turbopack (via next dev --turbopack) will fail with a “Next.js package not found” error if there is a pnpm-lock.yaml file inside that app’s directory (e.g. apps/web/pnpm-lock.yaml). Removing the stray pnpm-lock.yaml from apps/web immediately resolves the issue.

[AkbarAlam]

I had to remove the --turbo flag in the package.json. then it worked

[wbinnssmith]

Thanks for the report! This error usually happens when Turbopack determined your project’s root directory based on a lockfile that exists further down the filesystem than where next is installed.

For example, something like this:

repo/
  package.json
  package-lock.json
  node_modules/next
  apps/
    my-app/
      package.json
      package-lock.json
      app/
        page.tsx

Here, Turbopack determined the root directory to be my-app, but Next.js is installed further up the tree.

You’ll need to either:

• Remove the lockfile inside my-app if possible, or
• Set turbopack.root in to next.config.js to your repository’s root directory (or wherever Next.js is installed), as described here

We’re working on a better way of communicating this problem, and exploring other approaches where the root directory can be better discovered automatically.