invalid name: "@angular/common"
See original GitHub issue➜ AngularJS2 git:(master) ✗ sudo npm install
Password:
npm ERR! Darwin 15.0.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v5.10.1
npm ERR! npm v3.8.3
npm ERR! Invalid name: "@angular/common"
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/Austin/Projects/AngularJS2/npm-debug.log
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Installation problem - invalid packages names #2187 - GitHub
Mac OSX El Capitan Node 5.2.0, 6.0.0., 6.6.0 I'm trying to install the latest version of angular-cli: npm uninstall -g angular-cli npm cache ......
Read more >Top 5 @angular/common Code Examples - Snyk
Learn more about how to use @angular/common, based on @angular/common code ... reset the invalid state this.invalid = false; // check if the...
Read more >i can't install angular version
I am trying to install the version of angular pro but I can't install it. Resources (screenshots, code snippets etc.)
Read more >Why Installation of a new module show 'npm ... - Ionic Forum
Invalid package name "@angular/common/http": name can only contain ... by changing “@angular/common/http”: “4.3.0”, instead of “@angular/http”: “4.0.0”,.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
After some digging into the problem, I found this discussion in angular repo: https://github.com/angular/angular/issues/8464. It seems like upgrading npm version should help.
@moonmaster9000 Updating npm to latest (4.5.0) helped in my case.