-
-
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?]: Can't use yarn anymore with Node 12.18.0 #5825
Comments
I believe as of 4.0.0 release Related #5823 |
@shinebayar-g |
Then you could try and install Yarn the way it's recommended in the docs: via Corepack. The gotcha is that Corepack wasn't shipped with Node 12, and the latest versions, even if installed manually, will not work on such an ancient Node.js version. You MAY try running:
then configuring Corepack in your repository by properly setting That being said, you should reeeeeaaaaalllly consider upgrading your Node.js version, for many reasons, Yarn 4 compatibility of which is the least important. |
@wojtekmaj Yes you are right I need to update Node.js and it was planned in our roadmap but we didn't expect that it would just break out of nowhere, anyway that versione of corepack with Node 12.18.0, I think with my codebase I can arrive to Node 14.15.0 but also with that version yarn is not working also with corepack, this is the error: Node 14.15.0
Output:
|
@Piero87 You're using Node.js 12.x which was end-of-life on 2022-04-30, 1.5 years ago. The two LTS versions after 12.x - i.e. 14.x and 16.x - are also end-of-life. In the meantime, the Node.js 12.x support was dropped in [email protected] with nodejs/corepack#227 |
I opened a thread to consolidate information at #5829. Closing this one as duplicate. |
Self-service
Describe the bug
Hi, since yesterday I can't use anymore yarn, with node 12.18.0, this is what I do before
now after last release when I do
yarn set version berry
I have this error:To reproduce
Environment
I have tried in a lots of systems
Additional context
No response
The text was updated successfully, but these errors were encountered: