-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Parcel v2 invokes yarn on a pnpm repo and spews errors #5950
Comments
You can run with
We haven't been able to track that down yet: #5036 / #4955
We are aware of that, you should install
|
Great to see it's all tracked then, feel free to close if this issue is redundant. Thanks for the fix tips, I'll try them. I did follow the migration guide, the header about images refers to "Importing assets from JS" which I'm not doing, I've specified my assets on the commandline with a wildcard. If the parcelrc thing is necessary for assets specified that way too, I suggest changing the header to make that clear. 🙂 |
Although one note, my issue isn't so much the lacking support for pnpm, but rather that parcel should fail when it does not detect a yarn repo rather than invoking yarn anyway. |
There's also the (uncommon) case that you don't have any lockfile |
Which falls under "we don't know your package manager", which should be met with an error instead of yarn being invoked on no basis. 🙂 |
So pnpm should now be working correctly. Do you still run into some problem that isn't already covered by some other issue I linked? |
Well, next I ran into
My store location is set using an env var: |
Adding the missing dependencies manually leads to
Which I think is tracked somewhere already. |
I found a workaround: setting |
PNPM is having issues while installing @parcel/ modules that are supposed to live at the root level directory. https://pnpm.io/npmrc#public-hoist-pattern parcel-bundler/parcel#5950 (comment)
🐛 bug report
Parcel v2 seems to want to install extra dependencies during compilation, but uses yarn to do this while my repo is pnpm and has no trace of yarn.
🎛 Configuration (.babelrc, package.json, cli command)
Fairly small repo, please check any config you need to see: https://gitlab.com/Marnes/public-ip-display/-/tree/parcel2
I don't think any particular configuration is relevant to copy here since the issue is with package managers.
🤔 Expected Behavior
If parcel wants to install extra dependencies automagically, it should detect the package manager with certainty or fail, not just invoke a wrong one. If no supported manager is detected, it should output informative messages telling the user what it wanted to do automagically so it can be done manually (i.e. which dependencies does it need). This is separate from what's asked in #3408.
😯 Current Behavior
pnpm compile
orparcel build src/*.* src/images/flags/* src/images/error-* --dist-dir extension
console output
yarn-error.log
Console output breakdown:
💁 Possible Solution
🔦 Context
My repo evergreens its dependencies but parcel1 is broken at the moment, saw a comment to try parcel2.
💻 Code Sample
https://gitlab.com/Marnes/public-ip-display/-/commit/c7750f84c3f7966d9f1923c4698d3cdd46a83b02
🌍 Your Environment
The text was updated successfully, but these errors were encountered: