There was a bug in some versions of npm that kept this from working, so you may need to go in and fix that up by hand. When npm is used to install itself, it is supposed to copy this special builtin configuration into the new install. The Node installer installs, directly into the npm folder, a special piece of Windows-specific configuration that tells npm where to install global packages. (See also the point below if you're running Windows 7 and don't have the directory %appdata% pm.) A brief note on the built-in Windows configuration Copy the npmrc file back into %ProgramFiles% odejs ode_modules pm.This will tell the new npm where the global installed packages are. Go into %ProgramFiles% odejs ode_modules pm and copy the file named npmrc in the new npm folder, which should be %appdata% pm ode_modules pm.Npm install you installed npm with the node.js installer, after doing one of the previous steps, do the following. Then open cmd.exe as an administrator and run the following commands: Option 3: Navigate to %ProgramFiles% odejs ode_modules pm and copy the npmrcfile to another folder or the desktop. Remember that you'll need to restart cmd.exe (and potentially restart Windows) when you make changes to PATH or how npm is installed. Option 1: edit your Windows installation's PATH to put %appdata% pm before %ProgramFiles% odejs. On your PATH, it will always use the version of npm installed with node instead of the version of npm you installed using npm -g install get around this, you can do one of the following: Npm's globally installed packages (including, potentially, npm itself) are stored separately in a user-specific directory (which is currently By default, npm is installed alongside node in

Update node centos