Open
Conversation
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I'm implementing a version manager for Yarn, and Volta gets in the way: every call to
nodecorrupts the PATH by shadowing the existingyarnbinary.In theory Volta should be smarter and only update the PATH for binaries it's sure to own (see #2053), but in practice this is likely to be a significant change and I doubt we have the bandwidth to land this kind of change medium term.
Instead, this PR implements a
VOLTA_FEATURE_YARN=0environment variable that, when set, will prevent Volta from shadowing the Yarn binary. Any wrapper meant to own the management of Yarn releases can then set this variable.