fix(builtin): yarn_install
with vendored yarn .cjs
file breaks
#3350
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
yarn_install
allows for a vendored/custom Yarn JavaScript file. To ensurethat Yarn runs with the proper Node version,
yarn_install
calls the JS filewith the host NodeJS version also installed through Bazel. Currently the detection
logic does not account for
.cjs
or.mjs
. This is a little confusing as theinstall continues to work but breaks surprisingly in Windows then, or when a engines
requirement is no longer satisifed (there are more reasons as well)
We should support
cjs
andmjs
to avoid confusion, and especiallycjs
since Yarn itself always vendors itself with that extension!
Fixes #3349