Error: Refusing to delete: /usr/local/bin/npm

[bdielman]

I installed Node via Homebrew after a reinstall of my OS. Trying to run npm update -g and getting the following error which I've never come across before.

npm ERR! error rolling back Error: Refusing to delete: /usr/local/bin/npm not in /usr/local/lib/node_modules/npm
npm ERR! error rolling back     at clobberFail (/usr/local/Cellar/node/0.10.15/lib/node_modules/npm/lib/utils/gently-rm.js:41:12)
npm ERR! error rolling back     at next (/usr/local/Cellar/node/0.10.15/lib/node_modules/npm/lib/utils/gently-rm.js:27:14)
npm ERR! error rolling back     at /usr/local/Cellar/node/0.10.15/lib/node_modules/npm/lib/utils/gently-rm.js:36:12
npm ERR! error rolling back     at Object.oncomplete (fs.js:107:15)
npm ERR! error rolling back  npm@1.3.7 { [Error: Refusing to delete: /usr/local/bin/npm not in /usr/local/lib/node_modules/npm] code: 'EEXIST', path: '/usr/local/bin/npm' }
npm ERR! Refusing to delete: /usr/local/bin/npm not in /usr/local/lib/node_modules/npm
File exists: /usr/local/bin/npm
Move it away, and try again.

On Node v0.10.15 and npm v1.3.5.

[Ashot-KR]

got same error

[rainder]

same issue

[markson]

same here

[isaacs]

1. Uninstall the node and npm homebrew packages.
2. Go to http://nodejs.org/ and click the big green button.
3. Run the downloaded pkg, and follow the prompts.
4. Now everything works as intended.

[nikolay]

@isaacs Homebrew is a pretty popular package manager with many benefits and you should not ignore it. You can't advise people not to use it! Can you at least skip self-update under Homebrew? Nobody really cares if they are using the latest and greatest npm, but do care about other packages.

[luk-]

@nikolay

Having npm be skipped on updates is not something we can do, as it would change an expected semantic of npm for a single package. This is confusing for users, and sends us (contributors and maintainers) down a path of unreasonable functionality/code maintenance.

However, if this issue is major pain point for a lot of people, perhaps we can check with the homebrew folks if there's a way for them to handle the npm install differently. I'm not sure if this is possible with how and where homebrew installs things, but that doesn't mean it's not worth a try. Should there be a solution from this angle, it would be a long-term solution instead of a quick fix that will introduce technical debt.

[nikolay]

@luk- Now thinking about it, I have to agree with you - maybe fixing it in Homebrew would be best. Let me look into their "formula" and I will get back to you!

[nikolay]

@luk- Yes, they can definitely fix it on their end by changing a symlink. I will try submitting a patch.

[MikeMcQuaid]

Homebrew dev here: if you want to submit an issue to us about this please clarify what the expected behaviour is, what the actual behaviour is and (ideally) submit a pull request with the actual fix.

[nikolay]

@MikeMcQuaid I will submit the patch tonight or tomorrow. I will provide all the required info. Thanks!

[mysterycommand]

2 months ago? What happened?

[robsonpeixoto]

News? I'm having this problem.

[moollaza]

me too...