0
0
mirror of https://github.com/nodejs/node.git synced 2024-12-01 16:10:02 +01:00
nodejs/deps/npm/node_modules/npmconf
2012-12-12 14:41:28 -08:00
..
node_modules/config-chain npm: Upgrade to v1.1.69 2012-12-12 14:41:28 -08:00
test npm: Upgrade to 1.1.61 2012-09-10 09:11:54 -07:00
.npmignore
config-defs.js npm: upgrade to 1.1.62 2012-09-25 08:29:05 -07:00
LICENSE npm: upgrade to 1.1.62 2012-09-25 08:29:05 -07:00
npmconf.js npm: Upgrade to 1.1.61 2012-09-10 09:11:54 -07:00
package.json npm: Upgrade to v1.1.69 2012-12-12 14:41:28 -08:00
README.md

npmconf

The config thing npm uses

If you are interested in interacting with the config settings that npm uses, then use this module.

However, if you are writing a new Node.js program, and want configuration functionality similar to what npm has, but for your own thing, then I'd recommend using rc, which is probably what you want.

If I were to do it all over again, that's what I'd do for npm. But, alas, there are many systems depending on many of the particulars of npm's configuration setup, so it's not worth the cost of changing.

USAGE

var npmconf = require('npmconf')

// pass in the cli options that you read from the cli
// or whatever top-level configs you want npm to use for now.
npmconf.load({some:'configs'}, function (er, conf) {
  // do stuff with conf
  conf.get('some', 'cli') // 'configs'
  conf.get('username') // 'joebobwhatevers'
  conf.set('foo', 'bar', 'user')
  conf.save('user', function (er) {
    // foo = bar is now saved to ~/.npmrc or wherever
  })
})