-
Notifications
You must be signed in to change notification settings - Fork 27.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pnpm workspace package with non shared lockfile break dev mode #75226
Comments
For some reason I wrote that I had the same issue without turbopack. But seems if I remove the flag it's fixed |
Same exact issue here. Pnpm monorepo using turborepo with |
@LukasGerm Thank you for submitting an issue! I was able to replicate the issue. I have shared this with the team! |
off-topic: This also breaks vercel builds. When I try deploying something with cache, it breaks the deployment. Only when I redeploy without cache, it works. Error message:
|
@LukasGerm This is likely a separate configuration issue (your configuration on Vercel) since the issue above is related to Turbopack, which only runs on |
Link to the code that reproduces this issue
https://github.com/LukasGerm/pnpm-next-test
To Reproduce
Current vs. Expected behavior
Observe that
Expected would be that this works. Building the application works btw.
Provide environment information
Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:06:57 PDT 2024; root:xnu-11215.41.3~3/RELEASE_ARM64_T6041 Available memory (MB): 24576 Available CPU cores: 12 Binaries: Node: 20.9.0 npm: 10.1.0 Yarn: N/A pnpm: 9.15.4 Relevant Packages: next: 15.1.6 // Latest available version is detected (15.1.6). eslint-config-next: 15.1.6 react: 19.0.0 react-dom: 19.0.0 typescript: 5.7.3 Next.js Config: output: N/A
Which area(s) are affected? (Select all that apply)
Turbopack
Which stage(s) are affected? (Select all that apply)
next dev (local)
Additional context
I also tested without turbopack, but the same issue
The text was updated successfully, but these errors were encountered: