-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[Bug?]: Install instructions install 1.x instead of 3.x+ #6274
Comments
This should not happen if Corepack is properly enabled unless
The Corepack version that comes with Node 20.12.2 should be Corepack 0.25.2, which default to yarn v1.22.21. Check your
Also should not happen if Corepack is properly enabled |
Hmm, please define "properly" - from my understanding, it's just 1 command (above)? I'm on a fresh install of Win11, installed Node via nvm, installed node 20 and activated via nvm, then issues the corepack enable command. Does yarn have known issues with nvm? |
Looking at it again, I think the most likely scenario is you have a pinned version of yarn. Try Let's try this then
|
Not sure if its related but I'm having the reverse of this. I opened an issue on the original repo When I try install yarn v1 via This is on a M1 Mac |
I fixed it by running the following command:
Suggested by someone on stackoverflow. Might be useful here. Not really sure how berry got installed on my machine as I've never used it before. |
Just on my phone, but I'll be able to test this soon -- perhaps in a few days. Cheers for advice. |
Self-service
Describe the bug
https://yarnpkg.com/getting-started/install
These instructions are the same as the classic instructions, more or less, resulting in v 1.22.11 (which isn't even the classic stable version)
To reproduce
With node 20.12.2 (lts):
corepack enable
yarn -v
Environment
Additional context
The installation process to get to the correct latest stable version (3.x?) is wildly confusing with inaccurate best-practice installation steps. I tried to go to the Discord for help, but your website Discord link was also broken. Perhaps this hasn't been updated since 1.x?
The text was updated successfully, but these errors were encountered: