Turbopack Error: 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.

Turbopack version: fa536cf2

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.

[wbinnssmith]

hi @hqw567 -- yeah, this is correct. We’re working on a better way of communicating this problem, and exploring other approaches where the root directory can be better discovered automatically.

Thanks for the report!