Can not run globally installed packages which are installed with yarn

[sharikovvladislav]

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

Bug

What is the current behavior?
I can not run globally installed packages (uglifyjs, eslint etc).

Looks like there are problems with path. When I run (you full steps can see below) commands I get errors about path is incorrect. Path is: /d/Dev/nodejs/C:/Users/Vlad/AppData/Local/Yarn/config/global/node_modules/.bin/uglifyjs.
It is not problem with uglifyjs. If I will install eslint globally or something like that I am getting same behaviour.

I am trying to do this in Git Bash terminal (MINGW64). If I try to run same command in cmd, cmd window is just disappearing. I also tried to create .cmd file and run commands from this file via: cmdFileName >> xx.txt. I got this in output:

c:\Users\Vlad>eslint --help 
c:\Users\Vlad>"$basedir/C:/Users/Vlad/AppData/Local/Yarn/config/global/node_modules/.bin/eslint.cmd"   "$@" 
c:\Users\Vlad>exit $? 

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

1. Install yarn with windows installer.
2. Install uglify-js (or anything else) globally (from npm):
   Output is:

Vlad@VladPC MINGW64 /
$ yarn global add uglify-js
yarn global v0.17.10
warning No license field
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Installed uglify-js@2.7.5 with binaries:
      - uglifyjs
warning No license field
Done in 1.71s.

3. Use installed package

Vlad@VladPC MINGW64 /
$ uglifyjs
/bin/sh: /d/Dev/nodejs/C:/Users/Vlad/AppData/Local/Yarn/config/global/node_modules/.bin/uglifyjs: No such file or directory

What is the expected behavior?

I expect that I can run uglifyjs (or eslint or any other pacakges) command without errors after it.

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

NodeJS v 7.0.0
Yarn v v0.17.10
OS v Windows 7 Ultimate x64

[Daniel15]

Might be specific to Git Bash or MinGW... Try it in a regular cmd.exe and see if it works there?

[sharikovvladislav]

Nope. cmd.exe is not working too. When I write name of package cmd window just disappears. 12 Дек 2016 г. 3:45 пользователь "Daniel Lo Nigro" <notifications@github.com> написал:

…

Might be specific to Git Bash or MinGW... Try it in a regular cmd.exe and see if it works there? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2224 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFXK_jl2aerPmGRLeLRjCA3Mk-6mE8aaks5rHJkdgaJpZM4LKEVk> .

[builden]

+1
NodeJS v 7.0.0
Yarn v v0.18.1
Windows 7 Ultimate x64

after yarn global add http-server
http-server.cmd create at node.exe root dir

"$basedir/../../Users/{username}/AppData/Local/Yarn/config/global/node_modules/.bin/http-server.cmd"   "$@"
exit $?

console can't known the $bashdir path

[sharikovvladislav]

Hm. I am trying to get what is /d/Dev/nodejs/ prefix ($basedir). I don't even have this directory at the disk. I don't have any NODE_PATH env variable (or smth like that) with /d/Dev/nodejs/

[modulexcite]

I have the same exact problem when installing global packages using yarn and I have the same environment as @sharikovvladislav. I tried installing different packages globally with similar results and
none of the packages installed globally are available from cmd. Any help would be greatly appreciated.

[polizz]

Was able to repro. I tracked the issue down to the cmd-shim library.
There is an open PR that solves this.
When I updated my shim to the new code below, it executes as expected.

.....global\node_modules.bin\uglifyjs.cmd

@ECHO.%0 | FINDSTR /C:\ /C:/ >NUL && (
    SET dir=%~dp0
) || (
    FOR /F %%i IN ('where %0') DO @SET dir=%%~dpi
)
@IF EXIST "%dir%\node.exe" (
  "%dir%\node.exe" "%dir%\..\uglify-js\bin\uglifyjs %*
) ELSE (
  @SETLOCAL
  @SET PATHEXT=%PATHEXT:;.JS;=;%
  node "%dir%\..\uglify-js\bin\uglifyjs" %*
)

I did run into a separate issue where my Yarn bin path wasn't set correctly. I use the nodist node version manager on this machine. The choco Yarn install set C:\Users\andre\AppData\Local\Yarn\.bin, however the global installs were actually going to: C:\Users\andre\AppData\Local\Yarn\config\global\node_modules\.bin.

After manually setting that path, the above workaround script functioned as expected.

[markheron91]

I ran into this error as well, but before checking online I decided to try upgrading yarn to see if that fixed my problem - only problem is now the yarn package itself is showing this error. I've tried removing the files manually from the appData\local\yarn folder but it is still showing me the error.

Any idea how I can remove the packages from yarn and use npm instead for now as all of my work code written with angular-cli is now unusable until either this is fixed or I can get my "ng" command to point back to an npm version.

[modulexcite]

You should check the global folder %LocalAppData%\Yarn\config\global\node_modules% for any remnants of the globally installed packages using yarn and delete them manually if they are not removed after using yarn remove <package> --global. Also check the path of your node installation using where node from command line and delete any script files in the root directory named as your package that were installed globally using yarn. For example, I have node installed under %ProgramFiles(x86)\ndoejs% on a 64-bit machine and had to delete both ng and ng.cmd files when I installed angular-cli globally using yarn.

[markheron91]

@modulexcite ah, I had deleted all the files from the global/node_modules folder but I hadn't deleted the ones from inside the nodejs installation - thanks 😄

[modulexcite]

@markheron91 Glad to help, hopefully this will get fixed in the next release.

[iwsfg]

Nope. cmd.exe is not working too. When I write name of package cmd window just disappears.

Now that #1043 landed behaviour described in the quote is gone, but global packages still wont run from MINGW64. (At least it works from cmd). Here's what I'm seeing:

Iwasawafag@home:/c/dev/whatever (master)
$ where rimraf
C:\Program Files\nodejs\rimraf
C:\Program Files\nodejs\rimraf.cmd

Iwasawafag@home:/c/dev/whatever (master)
$ rimraf
/bin/sh: /c/Program Files/nodejs/../../Users/Iwasawafag/AppData/Local/Yarn/config/global/node_modules/.bin/rimraf: No such file or directory

Contents of both /c/Program Files/nodejs/rimraf and ~/AppData/Local/Yarn/config/global/node_modules/.bin/rimraf could be found in this gist

I guess for now I still have to use npm for installation of global packages if I want those to work in Git Bash

[enterit]

+1
In my case yarn install browserify creates a file D:\DevTools\nodejs\browserify.cmd:

@"%~dp0\C:\Users\myuser\AppData\Local\Yarn\config\global\node_modules\.bin\browserify.cmd"   %*

In this case executable path gets resolved to D:\DevTools\nodejs\\C:\Users\myuser\AppData\Local\Yarn\config\global\node_modules\.bin\browserify.cmd

This is obviously wrong.

To clarify, this only happens when I have Yarn installed via Chocolatey, and then Yarn is installed to C:\Program Files (x86)\Yarn\bin\yarn.cmd

If Yarn is installed using npm install -g yarn, then it gets installed to D:\DevTools\nodejs\yarn.cmd.
In this case yarn install -g browserify generates

@"C:\Users\myuser\AppData\Local\Yarn\config\global\node_modules\.bin\browserify.cmd"   %*

My Yarn version is 0.19.1.