npm registry manager
JavaScript
Latest commit ec88f5b Mar 17, 2014 @jarofghosts 0.5.0
Permalink
Failed to load latest commit information.
bin initial commit Feb 4, 2014
lib add --save-dev fix #5 Mar 17, 2014
test add support for devDependencies Mar 10, 2014
.travis.yml added testing data, travis config Feb 5, 2014
LICENSE initial commit Feb 4, 2014
README.md update readme and add --dosetup / -! Feb 23, 2014
index.js add --save-dev fix #5 Mar 17, 2014
package.json 0.5.0 Mar 17, 2014

README.md

npmm

Build Status

easy npm registry management

installation

npm install -g npmm

why

you decide when to use your private registry, the official registry, a mirror, etc.

how to use it

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:

{
  "dependencies@http://myprivate.npm": {
    "secret-module": "~1.2.3"
  }
}

...and then...

npmm install

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 from npm-registry-location.

alternatively:

npmm install --skipdefaults

which will only install dependencies outside of the standard dependencies, useful for using npmm as a dependency and adding a postinstall script to call it. This can be done automatically with:

npmm --dosetup or npmm -!

if npmm is not a standard dependency at the time this is run, its installation will be prepended to the postinstall script. (ie npm i npmm && npmm install --skipdefaults)

config options

optionally, if you would like to curate a config file, you can create ~/.npmm.json or 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": "http://location.of.npm"
  }
}
  • npm sets the location to the npm you want use (default "npm")
  • quiet will suppress npmm output, not npm output (default false)
  • registries can point names at locations, these are blank by default. this will allow for things like --save@work-npm on the command line, or dependencies@my-npm in your package.json.

notes

any other commands you throw at npmm will just get proxied to the real npm

license

MIT