Repository navigation
Cannot Install on Node v6 #548
Description
Cannot install angular-cli on newly released NodeJS v6.0.0.
- OS: Mac OSX El Capitan - 10.11.3
- Versions:
node --version: v6.0.0
npm --version: v3.8.6
npm info angular-cli: v0.0.34 - Reproduction Steps:
npm install -g angular-cli
- Log:
npm ERR! Darwin 15.3.0
npm ERR! argv "/Users/developer/.nvm/versions/node/v6.0.0/bin/node" "/Users/developer/.nvm/versions/node/v6.0.0/bin/npm" "install" "-g" "angular-cli"
npm ERR! node v6.0.0
npm ERR! npm v3.8.6
npm ERR! Invalid Version: 0.0.6pre2
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues>
npm ERR! Please include the following file with any support request:
npm ERR! /Users/developer/Desktop/npm-debug.log
- I'm aware NodeJS v6 just came out, so this is expected, but just thought I would post it here so others are aware.
Activity
alexpaluzzi commentedon Apr 27, 2016
Can you try clearing your npm cache? I was not able to reproduce on El Capitan or Windows 7/10. Both of them were able to install cleanly on Node 6.0.0 for me.
minhazfm commentedon Apr 28, 2016
Hey @alexpaluzzi, thanks for the information and tip. I tried an npm cache clean, and still got the same error. I am using nvm on my Mac to switch between different Node versions if that helps in someway. The strange thing is I'm able to install the angular-cli just fine when I'm running Node v4.2.2, but v6.0.0 produces the error above. I have installed other npm packages successfully in v6.0.0, such as bower, grunt-cli and yeoman as well.
jkuri commentedon Apr 28, 2016
@minhazfm this seems like an issue with
nvmand notangular-cli.minhazfm commentedon Apr 29, 2016
@jkuri Yup, looks like it was because I was running nvm v0.30.1. Once I updated to the latest nvm version (v0.31.0) it let me install the angular-cli with no issues. Thanks for the help, closing this out.
angular-automatic-lock-bot commentedon Sep 5, 2019
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.