-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Global install doesn't use %LocalAppData\Yarn\.bin #1226
Comments
I came across the same problem. And this is the main reason I do not use Yarn at the first time. |
This was fixed in 0.24.x |
If there is a "prefix" key-value in npm config file, yarn's globally added package would not be found because the "prefix" value(the path set for npm globally added packages) would be added before the yarn global bin path. Neither CMD nor Cmder would find that non-existed path. npm user config:
After globally adding
The path |
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
The Windows installer add %LocalAppData\Yarn.bin to the PATH (#1129).
After using
yarn global add [packages ...]
i did not found %LocalAppData\Yarn.bin, instead the bin is in %LocalAppData\Yarn\config\global\node_modules.binAdditionally
yarn global bin
is C:\Program Files\nodejs, so cmd are link from C:\Program Files\nodejs to %LocalAppData\Yarn\config\global\node_modules.binwe end up with three-way link:
nodejs ---> node_modules.bin ---> package.bin
If the current behavior is a bug, please provide the steps to reproduce.
yarn global add [packages ...]
What is the expected behavior?
yarn global bin
should point to %LocalAppData\Yarn.binPlease mention your node.js, yarn and operating system version.
Windows 10 Pro x64 v1607
node v6.9.0
yarn v0.16.0
The text was updated successfully, but these errors were encountered: