Replies: 36 comments 58 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.
-
|
same i use yarn and i downloaded latest version of next which is 15+ and I tried 22 and 20 version of node.js it still not working and when I remove the turbopackage It work. |
Beta Was this translation helpful? Give feedback.
-
|
yarn berry (yarn 4) was problematic for me too. Switching to yarn 1.22.19 helped. |
Beta Was this translation helpful? Give feedback.
-
|
For yarn berry you can't use the plug n play stuff, you need a .yarnrc.yml with |
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.
-
|
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.
-
|
For anyone reading this, make sure to delete the |
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.
-
|
worked in turborepo |
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 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.
-
|
Yep, just deleting extra package-lock, and it works. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
That was exactly my path: I moved an app created with This should be in the docs. If you point me in the right direction, I can document it. |
Beta Was this translation helpful? Give feedback.
-
|
This fixed it for me as well! next 15.3.3 pnpm 9.12.3 |
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.
-
|
Thanks Youse 🙏 |
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.
-
|
Instead of experimental.outputFileTracingRoot there is also experimental.turbo.root. I am getting the same PM2 loader errors if this value is set but this may work for others. |
Beta Was this translation helpful? Give feedback.
-
|
Is it possible uninstall --turbopack from my existing nextjs application? |
Beta Was this translation helpful? Give feedback.
-
|
still the same issue for clean install with create-next-app, next 15.1.6, bun v1.2, Debug info:
|
Beta Was this translation helpful? Give feedback.
-
|
retest in [email protected], server came up with bun workspaces and turbopack |
Beta Was this translation helpful? Give feedback.
-
|
+1 Have to rmrf |
Beta Was this translation helpful? Give feedback.
-
|
Same here. Running Next.js 15.0.3 with LogsInteresting enough, it starts just fine in the beginning ( |
Beta Was this translation helpful? Give feedback.
-
|
Could it be an m1 vs m2,3,4 issue? |
Beta Was this translation helpful? Give feedback.
-
|
Interesting... having the same issue (posted before) on M3 Pro. |
Beta Was this translation helpful? Give feedback.
-
|
Having this same issue with the M4 Pro Mac Mini after upgrading to the latest Nextjs. 15.1.7 and using Bun. Switching to canary like @larsilus said works. Canary .51 seems to be working correctly for me. |
Beta Was this translation helpful? Give feedback.
-
|
pnpm workspaces / monorepo people do this at root:
|
Beta Was this translation helpful? Give feedback.
-
|
it worked! thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Make sure you also delete all |
Beta Was this translation helpful? Give feedback.
-
|
I can confirm that using bun v1.2.2 workspaces and a text based lockfile, i encounter this issue. Upgrading to canary .56 fixed it. |
Beta Was this translation helpful? Give feedback.
-
|
Creating a bun.lockb dummy file solved the problem |
Beta Was this translation helpful? Give feedback.
-
|
I ended up switching to Yarn for now, but that's good to know thanks |
Beta Was this translation helpful? Give feedback.
-
|
this worked for me too, no idea why making a empty bun.lockb fixes it |
Beta Was this translation helpful? Give feedback.
-
|
Yooooo 😂😂😂 creating an empty bun.lockb fixed it! Not totally happy with this though, these bugs should be fixed asap, and both nextjs and bun team should collaborate closely always in all features, etc. |
Beta Was this translation helpful? Give feedback.
-
import path from 'node:path'
import type { NextConfig } from 'next'
const nextConfig: NextConfig = {}
if (process.env.NODE_ENV === 'development') {
nextConfig.outputFileTracingRoot = path.join(__dirname, '../../')
}
export default nextConfigI made this and worked for me in a monorepo (/apps/web) with bun. |
Beta Was this translation helpful? Give feedback.
-
|
Can confirm, works on next 15.1.6 too. |
Beta Was this translation helpful? Give feedback.
-
|
yup, works |
Beta Was this translation helpful? Give feedback.
-
|
It works great! 🎉 |
Beta Was this translation helpful? Give feedback.
-
|
Great this is the only solution that works! |
Beta Was this translation helpful? Give feedback.
-
|
it works in my project https://github.com/cycleccc/next-nest-monorepo import path from 'node:path';
import { fileURLToPath } from 'node:url';
const __filename = fileURLToPath(import.meta.url);
const __dirname = path.dirname(__filename);
/**
* Run `build` or `dev` with `SKIP_ENV_VALIDATION` to skip env validation. This is especially useful
* for Docker builds.
*/
import './src/env.js';
/** @type {import("next").NextConfig} */
const config = {
images: {
remotePatterns: [
{
hostname: 'avatar.vercel.sh',
},
],
},
outputFileTracingRoot: path.resolve(__dirname, '../../'),
};
export default config; |
Beta Was this translation helpful? Give feedback.
and others
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
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