The root of the the issue is really that npm is its own package manager and it is therefore better to have npm manage itself and its packages completely on its own instead of letting Homebrew do it.Īlso, using the Homebrew installation of npm will require you to use sudo when installing global packages. However, this is error-prone and still seems to cause problems for some people. The bug has been "fixed" by Homebrew installing npm in a way that allows it to manage itself once the install is complete.
There's an NPM bug for this exact problem. Npm ERR! /Users/dan/Google Drive/Projects/dotfiles/npm-debug.log Npm ERR! Additional logging details can be found in: Npm ERR! cwd /Users/dan/Google Drive/Projects/dotfiles Npm ERR! command "/usr/local/Cellar/node/0.10.26/bin/node" "/usr/local/bin/npm" "update" "npm" "-g" Npm ERR! Refusing to delete: /usr/local/bin/npm not in /usr/local/lib/node_modules/npm Npm ERR! error rolling back at Object.oncomplete (fs.js:107:15) Npm ERR! error rolling back at /usr/local/Cellar/node/0.10.26/lib/node_modules/npm/lib/utils/gently-rm.js:52:12 Npm ERR! error rolling back at next (/usr/local/Cellar/node/0.10.26/lib/node_modules/npm/lib/utils/gently-rm.js:43:14) Npm ERR! error rolling back at clobberFail (/usr/local/Cellar/node/0.10.26/lib/node_modules/npm/lib/utils/gently-rm.js:57:12) Npm ERR! error rolling back Error: Refusing to delete: /usr/local/bin/npm not in /usr/local/lib/node_modules/npm If you install node with Homebrew and then try to do npm update npm -g, you may see an error like this: $ npm update npm -g If you're a Homebrew user and you installed node via Homebrew, there is a major philosophical issue with the way Homebrew and NPM work together.
Now you can re-install any global npm packages you need without any problems.
0 kommentar(er)
