NPM Global install fail

Ever get the dreaded EACCES error after running npm install -g? You're not alone!

You will notice that npm is trying to install its packages to this path:

Missing write access to /usr/local/lib/node_modules

We need to change this to a better path that you have the rights to upate.

.npmrc update

using vim or nano update your local .npmrc file

vim ~/.npmrc

Update this file with the below, this will tell npm to install packages locally to .npm-packages

NPM Global install success

Once you change the .npmrc file, you will begin to install packages to ~/.npm-packages. No more issues

NPM init defaults

If you start projects using npm often enough you will want to default some of the authoring items. The basic syntax is npm config set init.*

Don't stress out if you are updating using npm config set while in a different directory this will still update in ~/.npmrc

Now our full .npmrc will look like:

Executing npm init will produce the following just by hitting enter.

Setting NPM registry

At work we have a VSTS (aka Visual Studio aka DevOps) private npm registry so it becomes important to use npm config set registry

Which will result in updating .npmrc with

There is a great medium article on setting up VSTS npm.

Setting NPM loglevel

Probably my favorite setting of all is npm config set loglevel="warn", this allows me to see any output and only the warnings. There are several different levels in the npm docs, you execute any of them by running something like below: