easy npm registry management
npm install -g npmm
you decide when to use your private registry, the official registry, a mirror, etc.
save dependencies to your
package.json automatically using
npmm install --save@http://myprivate.npm secret-module
or manually add a key to your
package.json like so:
anything in the standard
dependencies object will be installed from the
default registry (or the one designated in your
.npmrc if applicable) and
any packages in a
dependencies@npm-registry-location key will be installed
npmm install --skipdefaults
which will only install dependencies outside of the standard
useful for using npmm as a dependency and adding a postinstall script to call
it. This can be done automatically with:
npmm --dosetup or
if npmm is not a standard dependency at the time this is run, its installation
will be prepended to the postinstall script.
npm i npmm && npmm install --skipdefaults)
optionally, if you would like to curate a config file, you can create
project_dir/.npmm.json. the local config options will
always beat the global config options. what kind of options can you set? well
here are some:
"npm": "/usr/local/bin/npm""quiet": true"registries":"name": ""
npmsets the location to the npm you want use (default "
quietwill suppress npmm output, not npm output (default
registriescan point names at locations, these are blank by default. this will allow for things like
--save@work-npmon the command line, or
any other commands you throw at npmm will just get proxied to the real npm