Turbopack Error: Next.js package not found

[bogris]

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]

Hi, I am trying to chase details on how people run into this issue. Do you use a monorepo? is it possible to see the project that's running into this issue? Maybe you have Next.js globally installed somehow?

[bogris]

oh. this was fast. :))

i am running in a monorepo with pnpm. In order to get to this I did:

• create a folder: apps/lust
• installed next in it with create next package. (15.3)
• run pnpm dev >> this worked
• i moved the content of the folder into: /apps/lust/lust-web
• run pnpm dev >> this failed.

i tried:

• pnpm i
• pnpm i -f

running next in my terminal (home dir) errors with hot found. So i don;t think it's installed globally

i can't share the repo as its the main monorepo with all thing inside, but i can share bits and pices

i just checked now, the project runs without turbopack

[icyJoseph]

This was good, we got more info now, most people reporting the issue went silent... we'll get to the bottom of this

[icyJoseph]

Hi,

Are you using pnpm with PnP? I learned that yarn's PnP is not supported, and pnpm has some way to also use that.

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

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

I am trying to confirm if this is the case.

[bogris]

no, i am not using PnP.

But i got it working again. Unfortunately not in a deterministic way...

In order to solve some freak node build errors for lambda, something that i never had before, i removed all the node_modules packages and package.lock files, reinstalled and the esbuild errors went away

now i checked turbo dev and this works 2.

I think there were some broken links in the package links...

Do you want to try to get more info on this somehow?

[icyJoseph]

Not right now, if its working, so be it. You probably had fallen into a weird state with your node_modules and lock files, that made things break.

[bogris]

thanks for getting in this one!

great work on next15! 🚀