-
Notifications
You must be signed in to change notification settings - Fork 223
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
Incompatible version of yarn #233
Comments
@kylemh I'm glad you were able to fix the Yarn issue on Netlify by adding the |
Sure! I understand requiring Node 10.x, but why specify a specific version beyond that and why specify a specific version of yarn? |
This yarn engine requirement can break tests running in alpine linux node dockers as they might come with older yarn versions. I run into this lately as I use the following github action to run my tests: https://github.com/stefanoeb/jest-action (Which is using node 10 but with a not that new yarn version) Is there any reason you require yarn at all for this module? Why does it not work with npm or older versions of yarn? It was working fine with an old yarn in my projects for several months :) |
@ruisaraiva19 I feel like you should remove the requirement for a specific version of yarn. I doubt it affects local development. |
🎉 This issue has been resolved in version 7.11.1-canary.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 7.11.2-canary.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 7.11.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Thank you! <3 |
I was unable to install dependencies in Netlify because they use an older version of yarn.
I HIGHLY doubt there's anything wrong with
1.16.0
, can you please remove the engine requirements foryarn
?I've added
YARN_VERSION
to my build envs to use a more modern version of yarn, but my upgrade was also broken last week by an engine required version of Node... then that was reverted.Is there good reason to add these engine tags beyond
^10.x
for Node?The text was updated successfully, but these errors were encountered: