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
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.
Publish a package on a Windows system (yarn publish blah)
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
The text was updated successfully, but these errors were encountered:
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.
yarn publish blah
)yarn add blah
on a *nix systemWhat 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:
System used to add:
The text was updated successfully, but these errors were encountered: