-
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
Can't install package globally on Windows #859
Comments
Hi Same problem with Windows 7 Pro (x64) |
Seems to be happening where there's a dependency on abbrev as this is also impacting installing yo
Windows 10 Build 14396 Edit: I also tried manually installing abbrev:
Looks like abbrev may be a package which builds it's native version on the machine when it's installed via npm. |
Also in window10 (x64) , I can't globally install. In linking dependencies. This error:
|
Same here; Win10x64, node -v |
same here when installing karma global.
windows 8.1 enterprise x64 |
source: [https://github.com//issues/1073#issuecomment-254158785] It resolve by modifying the registry: add the double backlashes in registry. (yarn config set registry https://registry.yarnpkg.com//) |
@altyne that didn't work got a error 500 on packages and install failed |
I can also confirm this issue. Node 6.9.1 |
#1600 might be related |
Can you reproduce this with yarn global add pm2
yarn global v0.17.10
warning No license field
[1/4] Resolving packages...
[2/4] Fetching packages...
warning fsevents@1.0.15: The platform "win32" is incompatible with this module.
info "fsevents@1.0.15" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
[4/4] Building fresh packages...
[-/3] ⢀ waiting...
[2/3] ⠠ fsevents: gyp info using node@6.9.1 | win32 | x64
[-/3] ⠠ waiting...
[-/3] ⠠ waiting...
error Error running install script for optional dependency: <fsevents truncated>
success Installed pm2@2.1.6 with binaries:
- pm2
- rundev
- pm2-dev
- pm2-docker
warning No license field
Done in 92.80s. |
Still unable to install global packages with
|
@xt0rted that's a different error, as you're attempting to install into |
Hi, I've installed yarn@latest. pm2 was installed along with several errors and I can't use pm2 command at all. I've upgraded node js to 7.2.0 though, not sure if it's related.
try to use pm2:
|
I get the same error as @wtchangdm
I have Windows 7 x64 / Node 7.2.0 |
Errors from @zaggy and @wtchangdm seem to be from node-gyp. Last Two Stack Traces might not be a Yarn Error Do The packages Work Ehrn Installed With Npm? Ps: Sorry About The Weird Capitalization. Something Is Not Working Well With Swiftkey And This Comment BOx On Github |
I have probably found what is the issue. It appears that when yarn installs modules globally it puts executables to this location: |
The above fix by @zaggy worked for me too. What I noticed with the I should also note that I installed Yarn using the |
@yanxyz Same thing happens with gulp-cli , if installed w/ admin rights , any gulp command crashes the terminal in my case |
@skhamoud Can confirm same issue. When yarn is installed from the msi installer and global packages are added from admin terminal, the resulting .cmd in C:\Program Files\nodejs for any package crashes the terminal. |
The crashing of the terminal is fixed in the pre-release 0.19.0 |
yeah, it tries to install into |
This should be fixed in 0.24.x |
If you install Yarn via npm, you'll need to manually add
%LocalAppData%\Yarn\bin to your path.
Sent from my phone.
On May 27, 2017 4:13 AM, "W.T. Chang" <notifications@github.com> wrote:
Hi, I just installed 0.24.5 by npm. It can install global package now but
still not executable.
C:\>yarn --version
0.24.5
C:\>yarn global add pm2
yarn global v0.24.5
warning No license field
[1/4] Resolving packages...
[2/4] Fetching packages...
warning fsevents@1.0.17: The platform "win32" is incompatible with this module.
info "fsevents@1.0.17" is an optional dependency and failed
compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░[4/4] Building fresh
packages...
success Installed "pm2@2.4.6" with binaries:
- pm2
- rundev
- pm2-dev
- pm2-docker
warning No license field
Done in 1.57s.
C:\>pm2 -v
'pm2' is not recognized as an internal or external command, operable
program or batch file.
C:\>
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#859 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAFnHSnpT3euiIcOkPGn4PgRffHF4Svzks5r9xYygaJpZM4KUo_K>
.
|
Installing npm modules globally din't work for me. |
In my case, my path variable was set at After removing the |
@lewisl9029 - Which version of Yarn do you have? That should have been fixed in the installer for 0.24.0: 5fc8539 |
@Daniel15 That makes sense. I installed Yarn quite a while ago so I wouldn't be surprised if I used an installer version prior to 0.24.0. Glad to know it should no longer be a problem for new users! |
I have this issue on Linux. I've installed polymer-cli globally, but
|
@dandv - This issue is specific to Windows, as it was an issue with the MSI installer. Any Linux issues are unrelated. Please file a separate one. |
Do you want to request a feature or report a bug?
bug
What is the current behavior?
unable to install package globally
If the current behavior is a bug, please provide the steps to reproduce.
yarn global add pm2
What is the expected behavior?
install package like
npm install -g pm2
Please mention your node.js, yarn and operating system version.
Windows 10 x64 Enterprise, version 1607 (build 14393.321)
node js 6.7.0
yarn 0.15.1
The text was updated successfully, but these errors were encountered: