# normally, with Homebrew, your user should own the entire `/usr/local` folder:įor bash users: add/append the following lines in ~/.bashrc # this is the root folder where all globally installed node packages will goĮxport NPM_PACKAGES="/usr/local/npm_packages"Įxport NODE_PATH="$NPM_PACKAGES/lib/node_modules:$NODE_PATH" # it means the permissions are wrong with your `/usr/local` folder, so fix it Setup npm new home: /user/local/npm_packages # run the following commands
HOMEBREW FOR MAC USERS GUIDE INSTALL
# - if you don't use `yarn` (), prefer LTS install node -without-npm # - if you want to use `yarn` (), you need latest 'node' # install node via Homebrew, but without npm # always a good idea to have the latest version of Homebrew # this next line removes all the existing global npm packages Re-install node without npm # run the following commands Run the following commands to remove all existing global npm packages, uninstall node and npm, re-install node with the right permissions, install npm as its own package, and configure the location npm modules to be installed.ġ. Also, once you’re finished, you won’t need to use sudo to install npm modules globally. At the end of the guide you’ll need to re-install them. This guide will have you remove all of those packages. The following steps will fix the error: npm: command not foundīefore we begin, make a note of any globally installed npm packages. However, their support was disappointing! Due to not finding a fix I was forced to use yarn for two months ha. Note: I did contact npm support through e-mail in late May, 2017, their response time was amazing. To properly fix this, use the steps below. With the latest release of node: 8.4.0 and npm: 5.4.0, installing node through Homebrew can cause problems for globally installed packages.
I’m a Homebrew user and I install node.js without npm. With the initial npm 5 release a few months ago, I immediately noticed a few issues with my local dev-setup.
0 kommentar(er)
