Replies: 26 comments 35 replies
This comment was marked as spam.
This comment was marked as spam.
-
|
I enocuntered the same error when I configured multi-workspace npm project. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, my project is a turborepo monorepo with multiple workspaces |
Beta Was this translation helpful? Give feedback.
-
|
my project is mono-repo(lerna + pnpm), there are two package-lock file in project, just del the nextjs's pkg-lock |
Beta Was this translation helpful? Give feedback.
-
|
same issue here using bun monorepos |
Beta Was this translation helpful? Give feedback.
-
|
Still relevant in |
Beta Was this translation helpful? Give feedback.
-
|
I have the same issue on next.js 14.0.1 and my project is a turborepo monorepo with multiple workspaces as well |
Beta Was this translation helpful? Give feedback.
-
|
Still facing this issue. |
Beta Was this translation helpful? Give feedback.
-
|
Same. Workaround: Just remove the flag --turbo. |
Beta Was this translation helpful? Give feedback.
-
|
Workaround would be to avoid hoisting of your For example for You can set default install strategy by creating Overall it's a bug in |
Beta Was this translation helpful? Give feedback.
-
|
I don't use monorepo. I'm only using yarn berry, but the same thing happens. |
Beta Was this translation helpful? Give feedback.
-
|
Has anyone fixed this issue using Turborepo + PNPM? |
Beta Was this translation helpful? Give feedback.
-
|
I am using turborepo, bun and nextjs with --turbo and I get the exact same error |
Beta Was this translation helpful? Give feedback.
-
That's exactly the same stack I'm using. Same error. |
Beta Was this translation helpful? Give feedback.
-
|
What's your workaround? |
Beta Was this translation helpful? Give feedback.
-
|
"scripts": { You should find in the dev field the following: "next dev --turbo", delete the --turbo, should look like the one above. Worked for me |
Beta Was this translation helpful? Give feedback.
-
|
Also experiencing this issue: |
Beta Was this translation helpful? Give feedback.
-
|
I solved this error by deleting |
Beta Was this translation helpful? Give feedback.
-
|
didnt work for me |
Beta Was this translation helpful? Give feedback.
-
|
It's not worked on |
Beta Was this translation helpful? Give feedback.
-
|
This did it for me. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
I also had this issue when I was migrating a next app to a monorepo. |
Beta Was this translation helpful? Give feedback.
-
|
This worked for me too ✅. delete your bun.lockb file... bascially i was testing some packages in another branch so my bun lock file was messed up |
Beta Was this translation helpful? Give feedback.
-
|
I'm getting this error on |
Beta Was this translation helpful? Give feedback.
-
|
update bun will fix this issue: |
Beta Was this translation helpful? Give feedback.
-
|
Doesn't work for me. Even a new repo (created with |
Beta Was this translation helpful? Give feedback.
-
|
It might be a bun issue. Using npm, it works! |
Beta Was this translation helpful? Give feedback.
-
|
Hello, everyone! I don't know if it could help someone, but I had a lot of these problems. I was using Bun as a monorepo package manager, but Bun has a bug that hoists or not depending on whether you use Hope it can help someone. |
Beta Was this translation helpful? Give feedback.
-
|
I think |
Beta Was this translation helpful? Give feedback.
-
|
It didn't work. The |
Beta Was this translation helpful? Give feedback.
-
|
I've cloned this repository to run some tests, and everything works fine, even the |
Beta Was this translation helpful? Give feedback.
-
|
I'm hitting this error while using pnpm and docker :( |
Beta Was this translation helpful? Give feedback.
-
|
use |
Beta Was this translation helpful? Give feedback.
-
|
In my case it was |
Beta Was this translation helpful? Give feedback.
-
|
This fixed my issue. I had my pnpm+next15 monorepo structure. The package-lock.json was taking precendence over the root pnpm-lock.json |
Beta Was this translation helpful? Give feedback.
-
|
This also fixed the issue for me. Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
Fixed my issue next 15.1 pnpm 9.12.2 |
Beta Was this translation helpful? Give feedback.
-
|
Same as me. Using yarn @4.3.1 with corepack and turbo. Removing --turbo solved the issues. But I want to using --turbo |
Beta Was this translation helpful? Give feedback.
-
|
Same with [email protected] and [email protected] |
Beta Was this translation helpful? Give feedback.
-
|
Again with [email protected] and [email protected] |
Beta Was this translation helpful? Give feedback.
-
|
Using pnpm workspaces, the solution was deleting all |
Beta Was this translation helpful? Give feedback.
-
|
Removing the |
Beta Was this translation helpful? Give feedback.
-
|
idk if this will help anyone, but i had a leftover deleting this fixed the build |
Beta Was this translation helpful? Give feedback.
-
|
hmmmm, these lock files, this fixed it for me too, in my case I was using a monorepo |
Beta Was this translation helpful? Give feedback.
-
|
fixed it. Thanks you! |
Beta Was this translation helpful? Give feedback.
-
|
My stack are pnpm, bun, turbopack. Since it keeps happening, i'm just moving to NPM. |
Beta Was this translation helpful? Give feedback.
-
|
Well, i had no idea how i fixed it but it's just an assumption because i haven't experienced it anymore eventho i use pnpm, bun and turbopack. It turns out i put my workspace code inside folder that's part of icloud sync. LoL |
Beta Was this translation helpful? Give feedback.
-
|
with me fixed by deleting all lock files than |
Beta Was this translation helpful? Give feedback.
-
|
This did it for me. I was using pnpm and I still had a npm lock file from when I boostrapped the project. |
Beta Was this translation helpful? Give feedback.
-
|
This should be the answer. |
Beta Was this translation helpful? Give feedback.
-
|
When using |
Beta Was this translation helpful? Give feedback.
-
|
This just started happening to me with pnpm v9.9.0 and next v15.0.3. I've tried every relevant suggestion above, to no avail. My app literally has one Here's the error: |
Beta Was this translation helpful? Give feedback.
-
|
What about deleting the |
Beta Was this translation helpful? Give feedback.
-
|
Error comes from here https://github.com/vercel/next.js/blob/v15.0.3/crates/next-core/src/next_import_map.rs#L991 |
Beta Was this translation helpful? Give feedback.
-
|
This worked for me! |
Beta Was this translation helpful? Give feedback.
-
|
Partially working here: getting now PM2 import errors. |
Beta Was this translation helpful? Give feedback.
and others
-
Summary
When running
npm run devwith the--turboflag I get some errors and I want to create an issue but it asks for a minimal reproduction repo and I don't have any idea how I could find what's causing these errors. The errors are the following:Additional information
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions