#Homebrew for mac 10.13 how to#
#Homebrew for mac 10.13 mac os x#
#Homebrew for mac 10.13 install#
#Homebrew for mac 10.13 update#
#Homebrew for mac 10.13 upgrade#

> removed them using brew uninstall yarn watchman node > brew ls yarn watchman node & brew ls npm helped me realize that. > brew uninstall -ignore-dependencies node > You can override this and force removal with: > because it is required by yarn, which is currently installed. > Error: Refusing to uninstall /usr/local/Cellar/node/15.0.1 > brew uninstall node gave me the following error: On Tue, at 2:18 AM Anand Rockzz commented on this gist.

Up what it is) or something like that, I don’t remember off the top of my Just use the - force flag when installing or the ignore-dependency ( look On Mon, at 5:08 PM Tony Brown commented on this gist.

#Homebrew for mac 10.13 install#

In addition, global install work also! thanks something went wrong.

#Homebrew for mac 10.13 upgrade#

This work for me, installed nvm via brew, we can use nvm to install node, after that npm upgrade normally.

#Homebrew for mac 10.13 update#

To test, you can try to update npm itself with npm i -g npm, restart your terminal session, then check if version is updated. You should be good to install npm global packages with no issues.

Install the desired node version: nvm install -lts or nvm install node.

bash_profile) and restart your terminal session.

Follow the nvm instructions (create its folder and place the variables in your ~/.

Check installed versions of node and uninstall them first.

Plus you get a handy way to install the current LTS version and switching between these versions: Now days (October 2019) is much easier to use nvm. I believe is right, this post very important but solution is quite outdated. Since one of the core ideas behind Homebrew is that apps can be installed without giving them root access, this is a bad idea. 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. Run the following commands to remove all existing global npm modules, uninstall node & npm, re-install node with the correct defaults, configure the location for global npm modules to be installed, and then install npm as its own pacakge.Įxport PATH= ' $HOME/.npm-packages/bin: $PATH ' After you're finished you'll need to re-install them. These instructions will have you remove all of those packages. Once you're finished, you also won't need to use sudo to install npm modules globally.īefore you start, make a note of any globally installed npm packages. This solution fixes the error caused by trying to run npm update npm -g. An explanation is also included at the end of this document. To fix it quickly, use the solution below. Installing node through Homebrew can cause problems with npm for globally installed packages.

#Homebrew for mac 10.13 mac os x#

Fixing npm On Mac OS X for Homebrew Users

#Homebrew for mac 10.13 how to#

I still believe it is better to manually install npm separately since having a generic package manager maintain another package manager is a bad idea, but the instructions below don't explain how to do that. Homebrew maintainers have fixed things and the options mentioned don't exist and won't work. I've kept it here for historical purposes, but it should no longer be used. It was only ever intended to fix a specific error message which has since been fixed. This entire guide is based on an old version of Homebrew/Node and no longer applies.