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

Windows: Can't install global package; error log included #1600

Closed
dheerajbhaskar opened this issue Nov 1, 2016 · 3 comments
Closed

Windows: Can't install global package; error log included #1600

dheerajbhaskar opened this issue Nov 1, 2016 · 3 comments
Labels

Comments

@dheerajbhaskar
Copy link

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

What is the current behavior?

  1. do yarn global add angular-cli
  2. ng installs successfully but is not available on PATH

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

  1. do yarn global add angular-cli
  2. ng installs successfully but is not available on PATH

What is the expected behavior?
you should be able to run ng in the current cmd after installation or in a new cmd instance

Please mention your node.js, yarn and operating system version.
C:\my-home\WebStormProjects\ng-test>node --version
v6.4.0
C:\my-home\WebStormProjects\ng-test>yarn --version
0.16.1

Windows version:
Screenshot of  winver

Yarn Error log:
https://gist.github.com/dheerajbhaskar/d41589b8d74dd2b817b8e5f0ddb3bf37

Possible issues:

  • Permission issues (based on cursory look at the error log)
    • I installed yarn for current user using the windows installer (not via npm, if that's even possible), could this be an issue?
@artmadeit
Copy link

artmadeit commented Nov 17, 2016

Exactly same problem here...is there any news?

@dheerajbhaskar dheerajbhaskar changed the title yarn global crashing; error log included Windows: Can't install global package; error log included Nov 19, 2016
@OmgImAlexis
Copy link

Duplicate: #859

@voxsim
Copy link
Contributor

voxsim commented Apr 28, 2017

@bestander we can close this because it is a duplicate

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

No branches or pull requests

6 participants