Turbopack Error: Next.js package not found

[prosafwan]

Turbopack version: v15.4.2-canary.54-9-gff756b2c7
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

Note : Both yarnrc.yml and yarn dev --turbo=false are working. are there any alternatives to these two approaches?
Use: next js 15 and node 20

[tareq0065]

You’re hitting a known compatibility gap: Turbopack doesn’t support Yarn Plug-n-Play (PnP). That’s why it can’t “find” the next package under PnP, and why things work either (a) when you switch Yarn to node-modules via .yarnrc.yml, or (b) when you turn Turbopack off. This isn’t a local misconfig—Next’s own docs explicitly say PnP isn’t supported with Turbopack. ([Next.js]1)

Practical alternatives (that keep Turbopack on)

Pick any one of these—no need to use .yarnrc.yml or --turbo=false.

1. One-off env var (no repo config change)
   Use Yarn with node_modules just for this shell:

# from your app workspace
YARN_NODE_LINKER=node-modules yarn install
yarn dev --turbo

Yarn allows overriding settings via env vars, so you don’t need a .yarnrc.yml file for this. ([yarnpkg.com]2, [GitHub]3)

2. Switch to npm or pnpm for this app (node_modules linking)
   Both use node_modules by default and work fine with Turbopack:

# npm
rm -rf node_modules .pnp.* .yarn/cache
npm i
npm run dev -- --turbo

# pnpm
rm -rf node_modules .pnp.* .yarn/cache
pnpm i
pnpm dev --turbo

(If you’re in a monorepo, run these in the app workspace so next is a direct dependency of the app.)

3. Workspace-local config only (scoped)
   If you want Yarn across the repo but only flip this app:

# in apps/your-next-app/.yarnrc.yml
nodeLinker: node-modules

This keeps PnP elsewhere while making this workspace Turbopack-compatible.

Quick health checks (avoid common gotchas)

• Ensure next, react, and react-dom are declared in the app’s package.json (not just the repo root). Run: yarn workspace <app> add next@^15 react@^19 react-dom@^19.
• Run yarn why next to confirm the app resolves the real Next package (not a misnamed local workspace).
• Delete caches: rm -rf .next node_modules .pnp.* .yarn/cache then reinstall.
• Stay on Node 20 x64 (you said Node 20—good). Some Windows reports blamed wrong Node arch; the fix was reinstall x64 and clean caches. ([Stack Overflow]4)

About the “Next.js version: 0.0.0”

That printout is a known logging quirk seen alongside canary Turbopack builds; it doesn’t necessarily reflect your installed next version. ([GitHub]5)

---

Bottom line: There’s no supported way to run Turbopack + Yarn PnP today. Use node_modules linking via a temporary env var, a workspace-local .yarnrc.yml, or switch this app to npm/pnpm—any of those will let you keep Turbopack on. If you still see “Next.js package not found” after moving off PnP, it’s usually project-root resolution or a Yarn 4/PnP residual—see similar reports and fixes in the Next issues. ([GitHub]6)