Skip to content
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.

Sign up for GitHub

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

Jump to bottom

yarn policies on Windows 10 generates invalid *nix paths #7777

Closed
wegry opened this issue Dec 20, 2019 · 1 comment
Closed

yarn policies on Windows 10 generates invalid *nix paths #7777

wegry opened this issue Dec 20, 2019 · 1 comment

Comments

@wegry
Copy link

wegry commented Dec 20, 2019

Do you want to request a feature or report a bug?

Report a bug

What is the current behavior?

Using yarn policies on Windows generates a yarn-path in the .yarnrc file with backslashes.

.yarn\\releases\\yarn-1.21.1.js

This breaks *nix boxes trying to use the same .yarnrc.

If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?

Regardless of operating system, the yarn-path should contain forward slashes.

.yarn/releases/yarn-1.21.1.js

Please mention your node.js, yarn and operating system version.

Node@12.14.0, yarn@1.21.1, Windows 10/Ubuntu 18.04
This was referenced Jan 31, 2020
Closed
Closed
@merceyz
Copy link
Member

merceyz commented Jan 2, 2021

Fixed in #7862

@merceyz merceyz closed this as completed Jan 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: force to use / as a path separator in yarn-path exKAZUu/yarn
2 participants
@merceyz @wegry