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
When on Windows, yarn policies set-version x.xx will set yarn-path in .yarnrc file, however it will insert backslashes (\\), rather than forward slashes /. When then grabbing that repo on a non-Windows platform, yarn is just broken, causing cryptic, unrecoverable error messages any time you use any yarn command (even the ones that are suggested to repair such errors):
Bug description
Yarn Command
What is the current behavior?
When on Windows,
yarn policies set-version x.xx
will setyarn-path
in.yarnrc
file, however it will insert backslashes (\\
), rather than forward slashes/
. When then grabbing that repo on a non-Windows platform,yarn
is just broken, causing cryptic, unrecoverable error messages any time you use any yarn command (even the ones that are suggested to repair such errors):What is the expected behavior?
Yarn should not break.
One possible way to fix it would be to have
yarn-path
just use forward slashes.If cross-platform is not desired, at least a proper error message would be useful.
Environment
yarn-policies
on Windows, then trying to run it on non-Windows system.References
yarn policies
modifies yarn-path and then breaks yarn when moving from Windows to *nix #8040 but I felt, it was not concise enough, so re-writing it here.yarn-path
is a more general issue, also discussed inyarn config delete yarn-path
doesn't work if yarn-path is invalid #6896The text was updated successfully, but these errors were encountered: