Turbopack Error: Next.js package not found

[ngankilo]

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

[icyJoseph]

I keep seeing this error every other day... 🤔

I had the same error today. Deleting the pnpm-lock.yaml file and re-installing fixed that issue for me. But that is just a workaround!

Could you share more details about your repository?

[ngankilo]

With the following environment configuration:
Operating System: macOS
Node.js: v22.14.0
Yarn: 4.9.1

Project: https://github.com/ngankilo/landingpage

[ngankilo]

I also tried deleting node_modules and package-lock.json, but the error still occurs when running yarn dev.

[icyJoseph]

Awesome mate, I'll try to deep dive into this! Thanks!

[ngankilo]

Great to hear that!
I'm glad you’re diving deeper into it. If you run into any issues or have questions along the way, just give me a shout.
Happy coding!

[icyJoseph]

Is that it really? no more? just creating create-next-app causes this? I ran the project on Stackblitz, and it works fine there.

[ngankilo]

No joke, my friend — I just tried again and I'm still getting this error.

[icyJoseph]

I wonder if its a PnP issue, I need to take a break now, but I think we are moving in the right direction here.

[ngankilo]

Haha, with the goal of making Next.js better, if there's an issue, We need to have all the info We can to trace the bug.

[icyJoseph]

Yes, so, yarn v4, with PnP

The way Yarn PnP works, it tells Yarn to generate a single Node.js loader file in place of the typical node_modules folder. This loader file, named .pnp.cjs, contains all information about your project's dependency tree, informing your tools as to the location of the packages on the disk and letting them know how to resolve require and import calls.

[icyJoseph]

And we come full circle, https://nextjs.org/docs/app/api-reference/turbopack#unsupported-and-unplanned-features:

• Yarn PnP Not planned for Turbopack support in Next.js.

[icyJoseph]

If you want to keep on using that yarn version, you have to switch to node_modules linker, by creating .yarnrc.yml file with these contents:

nodeLinker: node-modules

[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.

[nikelborm]

I use Docker.
My solution for the error was adding a missing bun.lock file into my monorepo's development container. The issue was even with package.json, node_modules, .turbo files and folders present, but with the absence of bun.lock

[r34son]

But problems can happen if you use https://pnpm.io/settings/#virtualstoredir outside the project root. @wbinnssmith, @icyJoseph, @timneutkens, do you need a reproduction for this or can you reproduce it yourself? Just add virtual-store-dir=~/.cache/pnpm/virtual-store/next-app to your app's root .npmrc file and reinstall packages
Webpack works fine

[r34son]

Is it unsupported and unplanned? https://nextjs.org/docs/app/api-reference/turbopack#unsupported-and-unplanned-features