node/deps/npm/man/man3/init.3
isaacs 054127112c Upgrade npm to 1.1.3
* Update request to support HTTPS-over-HTTP proxy tunneling
* Throw on undefined envs in config settings
* Update which to 1.0.5
* Fix windows UNC busyloop in findPrefix
* Bundle nested bundleDependencies properly
* Alias adduser to add-user
* Doc updates  (Christian Howe, Henrik Hodne, Andrew Lunny)
* ignore logfd/outfd streams in makeEnv() (Rod Vagg)
* shrinkwrap: Behave properly with url-installed deps
* install: Support --save with url install targets
* Support installing naked tars or single-file modules from urls etc.
* init: Don't add engines section
* Don't run make clean on rebuild
* Added missing unicode replacement (atomizer)
2012-03-02 09:31:46 -08:00

40 lines
1.1 KiB
Groff

.\" Generated with Ronnjs/v0.1
.\" http://github.com/kapouer/ronnjs/
.
.TH "INIT" "3" "March 2012" "" ""
.
.SH "NAME"
\fBinit\fR \-\- Interactively create a package\.json file
.
.SH "SYNOPSIS"
.
.nf
npm\.commands\.init(args, callback)
.
.fi
.
.SH "DESCRIPTION"
This will ask you a bunch of questions, and then write a package\.json for you\.
.
.P
It attempts to make reasonable guesses about what you want things to be set to,
and then writes a package\.json file with the options you\'ve selected\.
.
.P
If you already have a package\.json file, it\'ll read that first, and default to
the options in there\.
.
.P
It is strictly additive, so it does not delete options from your package\.json
without a really good reason to do so\.
.
.P
Since this function expects to be run on the command\-line, it doesn\'t work very
well as a programmatically\. The best option is to roll your own, and since
JavaScript makes it stupid simple to output formatted JSON, that is the
preferred method\. If you\'re sure you want to handle command\-line prompting,
then go ahead and use this programmatically\.
.
.SH "SEE ALSO"
npm help json