-
Notifications
You must be signed in to change notification settings - Fork 147
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
fix: don't ignore engines with yarn v2+ #831
Conversation
Codecov Report
@@ Coverage Diff @@
## main #831 +/- ##
==========================================
+ Coverage 96.05% 96.12% +0.06%
==========================================
Files 31 31
Lines 913 929 +16
==========================================
+ Hits 877 893 +16
Misses 36 36
Continue to review full report at Codecov.
|
This comment has been minimized.
This comment has been minimized.
CI (using nodejs/node#35332 to avoid the umask deprecation noise): https://ci.nodejs.org/job/citgm-smoker/2483/ |
133de60
to
e7e5f21
Compare
40b52e0
to
a166fd4
Compare
yarn v2 doesn't support the `YARN_IGNORE_ENGINES` environment variable. We still need to set `YARN_IGNORE_ENGINES` for older versions of yarn to allow installation with unreleased versions of Node.js. Projects are able to use yarn policies to set the version of yarn they are using, so we need to version sniff to determine whether or not to set the environment variable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RSLGTM
yarn v2 doesn't support the
YARN_IGNORE_ENGINES
environment variable.We still need to set
YARN_IGNORE_ENGINES
for older versions of yarnto allow installation with unreleased versions of Node.js. Projects are
able to use yarn policies to set the version of yarn they are using,
so we need to version sniff to determine whether or not to set the
environment variable.
Fixes: #824
Checklist
npm test
passeshere