mirror of https://github.com/nodejs/node.git
f76c3938d0
* Check SHA before using files from cache * adduser: allow change of the saved password * Make `npm install` respect `config.unicode` * Fix lifecycle to pass `Infinity` for config env value * Don't return 0 exit code on invalid command * cache: Handle 404s and other HTTP errors as errors * bump tap dep, make tests stderr a bit quieter * Resolve ~ in path configs to env.HOME * Include npm version in default user-agent conf * npm init: Use ISC as default license, use save-prefix for deps * Many test and doc fixes |
||
|---|---|---|
| .. | ||
| example | ||
| node_modules/promzard | ||
| test | ||
| LICENSE | ||
| README.md | ||
| default-input.js | ||
| init-package-json.js | ||
| package.json | ||
README.md
init-package-json
A node module to get your node module started.
Usage
var init = require('init-package-json')
var path = require('path')
// a path to a promzard module. In the event that this file is
// not found, one will be provided for you.
var initFile = path.resolve(process.env.HOME, '.npm-init')
// the dir where we're doin stuff.
var dir = process.cwd()
// extra stuff that gets put into the PromZard module's context.
// In npm, this is the resolved config object. Exposed as 'config'
// Optional.
var configData = { some: 'extra stuff' }
// Any existing stuff from the package.json file is also exposed in the
// PromZard module as the `package` object. There will also be free
// vars for:
// * `filename` path to the package.json file
// * `basename` the tip of the package dir
// * `dirname` the parent of the package dir
init(dir, initFile, configData, function (er, data) {
// the data's already been written to {dir}/package.json
// now you can do stuff with it
})
Or from the command line:
$ npm-init
See PromZard for details about what can go in the config file.