angular-cli installation fails renaming /usr/local/lib/node_modules/.staging/abbrev

[manuelfink]

Environment

Mac on latest El Capitan
node v6.2.2 with npm 3.10.2

Repro steps.

• trying to upgrading to latest cli tools (sudo npm install -g angular-cli or sudo npm update -g angular-cli not sure which i run)
• angular-cli / npm broken
• reintalling node
• trying to install angular-cli again
• intallation allways fails

Error

$  sudo npm install -g angular-cli
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
/usr/local/lib
└── (empty)

npm ERR! Darwin 15.5.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "angular-cli"
npm ERR! node v6.2.2
npm ERR! npm  v3.10.2
npm ERR! path /usr/local/lib/node_modules/.staging/abbrev-432cdd5a
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall rename

npm ERR! enoent ENOENT: no such file or directory, rename '/usr/local/lib/node_modules/.staging/abbrev-432cdd5a' -> '/usr/local/lib/node_modules/angular-cli/node_modules/ember-cli/node_modules/npm/node_modules/abbrev'
npm ERR! enoent ENOENT: no such file or directory, rename '/usr/local/lib/node_modules/.staging/abbrev-432cdd5a' -> '/usr/local/lib/node_modules/angular-cli/node_modules/ember-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!     /Users/manuelfink/git/angular-2-cli-test/ContentFlows/npm-debug.log
npm ERR! code 1

[mikeybyker]

+1

[manuelfink]

UPDATE: uninstalling and reinstalling angular-cli should fix the issue:

as mentioned by @nikokosh and @davidrensh below try:

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

This worked for me in the latest versions as well.

Original quick fix: reinstalling node

Somehow in earlier angular-cli version it seemed to me angular-cli somehow broke node installation. Manual fix, uninstalling and reinstalling node completely fixed the issue for me. hope i didn't forget anything:

#### uninstalling globally installed libs
sudo npm uninstall -g angular-cli
#### uninstall other libs
sudo npm uninstall -g

#### uninstalling node
sudo rm -rf /usr/local/{lib/node{,/.npm,_modules},bin,share/man}/{npm*,node*,man1/node*}
rm -rf /Users/[homedir]/.npm

#### reinstall node

#### update npm to latest
sudo npm install -g npm

#### reinstall angular-cli
sudo npm install -g angular-cli

[kylecordes]

Related to this: the procedure in the "upgrade guide":

https://github.com/angular/angular-cli#updating-angular-cli

is very off-putting, a negative quality signal. Many, many developers upgrade many NPM packages every day, without throwing away their NPM cache (!!).

To make these instruction confidence-inspiring, there should be:

• Explanation, even brief, of why this package (unlike countless others) requires throwing away the whole NPM cache for each upgrade.
• Hopefully a pointer to some known NPM defect that temporarily justifies the instructions.

[alexciesielski]

+1, Windows 10, running cmd as admin

npm v3.8.1
node v5.7.0

[KingTigerXCII]

+1
El Capitan,
npm 3.9.5,
node 6.2.2

@manuelfink thank you very much, works fine! :)

[filipesilva]

@manuelfink Very weird that it's breaking the global npm... I'll flag this as urgent but I don't have a linux machine to debug myself.

@kylecordes Angular-CLI uses the same upgrade guide as Ember-CLI because it is essentially an Ember-CLI addon. See https://github.com/ember-cli/ember-cli/releases

[coxjonc]

+1
El Capitan,
npm 3.10.5
node 6.3.0

[aeb0]

+1
Yosemite
npm 3.5.3
node 5.5.0

kylecordes link works for fix:
https://github.com/angular/angular-cli#updating-angular-cli

[anas7asia]

I had the same problem on El Capitan
node 6.2.1
npm 3.9.3.

It was solved by simple uninstall of angular-cli:
sudo npm uninstall -g angular-cli

And its immediate reinstalling:
sudo npm install -g angular-cli

Without npm reinstalling you can keep your cache and all the dependencies as it was.

[davidrensh]

Solved by (nothing else):
npm uninstall -g angular-cli
npm install -g angular-cli

[mac-bhaird]

+1
Windows 10 64 bit

Also solved by @davidrensh solution:
npm uninstall -g angular-cli
npm install -g angular-cli

[roelvanlisdonk]

I had the same problem and it was also solved by @davidrensh solution:
npm uninstall -g angular-cli
npm install -g angular-cli

windows 10 64 bit
node v6.4.0
npm v3.10.3

[looselytyped]

@nikokosh and @davidrensh solution worked for me as well. No need to reinstall npm, or node. Simply npm uninstall -g angular-cli then npm install -g angular-cli