-
Notifications
You must be signed in to change notification settings - Fork 520
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
docs: caveats of multiple package managers #640
Comments
document potential issue when multiple versions of pnpm are installed while using corepack closes pnpm#640
You had pnpm v9 installed. With pnpm v10 you wouldn't have noticed any issue as it would switch to the right pnpm version automatically. So, I don't think a notice is needed. |
For me that is where the confusion came in. I think in my case what caused this confusion is corepack could not install the new version after throwing a Eventually I noticed the version miss match and didn't understand why the version specified in the package.json was not used. But if you think the info is redundant, I can close the issue and docs pr. Thank you for taking the time to go through the issue :) |
I had an issue where pnpm was installed with corepack, but I would have a version mismatch when comparing the package manager in the package.json and the pnpm version in the terminal.
I created an issue with corepack: nodejs/corepack#659
After some debugging, we determined that I had 2 versions of pnpm installed.
One via corepack, and another via globally from npm.
See here as reference: nodejs/corepack#659 (comment)
I was then suggested to maybe add documentation to warn against this odd behaviour here: nodejs/corepack#659 (comment)
I am considering adding some information regarding this here: https://github.com/pnpm/pnpm.io/blob/main/docs/installation.md
on line 97.
The text was updated successfully, but these errors were encountered: