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.

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

Bad file paths when publishing on Windows (backslash in package file paths) #3031

Open
aautar opened this issue Apr 2, 2017 · 1 comment

Comments

@aautar
Copy link

aautar commented Apr 2, 2017

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

What is the current behavior?
Packages published via yarn publish, on Windows, seem to use backslash as a path separator for file paths. This becomes a problem when these packages are added on *nix systems where the backslash is interpreted as part of the filename and not as a directory separator.

So if a package is published, on Windows, with the following file path: dist/test.min.js
When added, on a *nix system, the file is downloaded and created as: dist\test.min.js

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

  1. Publish a package on a Windows system (yarn publish blah)
  2. Add that package as dependency to a project via yarn add blah on a *nix system

What is the expected behavior?
Directory structure of published folder from a Windows system will be retained when adding package on *nix system.

Please mention your node.js, yarn and operating system version.
System used to publish:

  • node v6.9.1
  • yarn v0.21.3
  • Windows 10 Home v1607 (64-bit)

System used to add:

  • node v7.8.0
  • yarn v0.21.3
  • Ubuntu 14.04
@BYK
Copy link
Member

BYK commented Oct 27, 2017

@aautar is this still an issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants