You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug?]: YARN_IGNORE_PATH doesn't affect scripts that call yarn #7309
And you need a .yarnrc.yml with a yarnPath pointing to a different version of yarn than the one on your PATH. In the following console session, yarn from my PATH is 4.18.0, but my yarnPath points to 4.18.1.
Note that yarn correctly honors the configured yarnPath, but ignores it if YARN_IGNORE_PATH is set:
This behavior was introduced in #256, and seems to be understood:
One problem is that it causes the settings to never persist - so a user manually adding YARN_IGNORE_PATH in their environment might be confused to see that the local one will still get executed in the nested scripts.
This is one user being confused by this behavior.
It seems to me like the fix is to just undo #256. The PR description has a broken link explaining that we set YARN_IGNORE_PATH somewhere:
and since we set YARN_IGNORE_PATH the nested global instances never reexecute the local ones
I wonder if that behavior still exists and is truly necessary?
Activity