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

Installation fails on Windows #2436

Closed
alexliesenfeld opened this issue Sep 30, 2016 · 6 comments
Closed

Installation fails on Windows #2436

alexliesenfeld opened this issue Sep 30, 2016 · 6 comments

Comments

@alexliesenfeld
Copy link

alexliesenfeld commented Sep 30, 2016

Hi,

it seems at the moment there is a problem installing the CLI on Windows. This happened on a fresh node installation on Windows 7.

C:\Users\Alex>npm install -g angular-cli
npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm
ls graceful-fs' to find it in the tree.
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated lodash-node@2.4.1: This package is discontinued. Use lodash@^4.0.0.
npm WARN deprecated lodash.assign@4.2.0: This package is deprecated. Use Object.assign.
npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated tough-cookie@2.2.2: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
C:\Users\Alex\AppData\Roaming\npm
`-- (empty)

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\angular-cli\node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.0.14: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\Alex\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "install" "-g" "angular-cli"
npm ERR! node v4.6.0
npm ERR! npm v3.10.8
npm ERR! path C:\Users\Alex\AppData\Roaming\npm\node_modules.staging\abbrev-1ea80297
npm ERR! code ENOENT
npm ERR! errno -4058
npm ERR! syscall rename

npm ERR! enoent ENOENT: no such file or directory, rename 'C:\Users\Alex\AppData\Roaming\npm\node_modules.staging\abbrev-1ea80297' -> 'C:\Users\Alex\AppData\Roaming\npm
node_modules\angular-cli\node_modules\npm\node_modules\abbrev'
npm ERR! enoent ENOENT: no such file or directory, rename 'C:\Users\Alex\AppData\Roaming\npm\node_modules.staging\abbrev-1ea80297' -> 'C:\Users\Alex\AppData\Roaming\npm
node_modules\angular-cli\node_modules\npm\node_modules\abbrev'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! Please include the following file with any support request:
npm ERR! C:\Users\Alex\npm-debug.log
npm ERR! code 1

C:\Users\Alex>

@cclelio
Copy link

cclelio commented Oct 2, 2016

You can use this workaround

#1190

npm uninstall -g angular-cli
npm install -g angular-cli

@JanStureNielsen
Copy link

@asmsk -- the GitHub issue tracker is for project bugs and project feature requests as noted in CONTRIBUTING.md. For better support, consider creating a question on StackOverflow with all the details.

Upgrade to Node 6:

http://stackoverflow.com/questions/39812448/angular-cli-installation-failure

@alexliesenfeld
Copy link
Author

@cclelio and @JanStureNielsen: Thank you. After upgrading to the newest node version and uninstalling before installing globally everything worked out fine. Thanks.

@filipesilva
Copy link
Contributor

Dupe of #1190

@tech-tron
Copy link

@cclelio no clue why that worked, but it did and that's awesome

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants