deps: upgrade npm to 6.13.7

PR-URL: https://github.com/nodejs/node/pull/31558
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>

1 files changed, 842 insertions, 2 deletions

diff --git a/deps/npm/man/man7/config.7 b/deps/npm/man/man7/config.7
index 617b5354c1..ad67a24a3b 100644
--- a/deps/npm/man/man7/config.7
+++ b/deps/npm/man/man7/config.7
@@ -1,6 +1,846 @@
+.TH "CONFIG" "7" "January 2020" "" ""
+.SH "NAME"
+\fBconfig\fR \- More than you probably want to know about npm configuration
+.SS Description
 .P
-"
-```
+npm gets its configuration values from the following sources, sorted by priority:
+.SS Command Line Flags
+.P
+Putting \fB\-\-foo bar\fP on the command line sets the \fBfoo\fP configuration
+parameter to \fB"bar"\fP\|\.  A \fB\-\-\fP argument tells the cli parser to stop
+reading flags\.  Using \fB\-\-flag\fP without specifying any value will set
+the value to \fBtrue\fP\|\.
+.P
+Example: \fB\-\-flag1 \-\-flag2\fP will set both configuration parameters
+to \fBtrue\fP, while \fB\-\-flag1 \-\-flag2 bar\fP will set \fBflag1\fP to \fBtrue\fP,
+and \fBflag2\fP to \fBbar\fP\|\.  Finally, \fB\-\-flag1 \-\-flag2 \-\- bar\fP will set
+both configuration parameters to \fBtrue\fP, and the \fBbar\fP is taken
+as a command argument\.
+.SS Environment Variables
+.P
+Any environment variables that start with \fBnpm_config_\fP will be
+interpreted as a configuration parameter\.  For example, putting
+\fBnpm_config_foo=bar\fP in your environment will set the \fBfoo\fP
+configuration parameter to \fBbar\fP\|\.  Any environment configurations that
+are not given a value will be given the value of \fBtrue\fP\|\.  Config
+values are case\-insensitive, so \fBNPM_CONFIG_FOO=bar\fP will work the
+same\. However, please note that inside npm help \fBscripts\fP
+npm will set its own environment variables and Node will prefer
+those lowercase versions over any uppercase ones that you might set\.
+For details see this issue \fIhttps://github\.com/npm/npm/issues/14528\fR\|\.
+.P
+Notice that you need to use underscores instead of dashes, so \fB\-\-allow\-same\-version\fP
+would become \fBnpm_config_allow_same_version=true\fP\|\.
+.SS npmrc Files
+.P
+The four relevant files are:
+.RS 0
+.IP \(bu 2
+per\-project configuration file (\fB/path/to/my/project/\.npmrc\fP)
+.IP \(bu 2
+per\-user configuration file (defaults to \fB$HOME/\.npmrc\fP; configurable via CLI
+option \fB\-\-userconfig\fP or environment variable \fB$NPM_CONFIG_USERCONFIG\fP)
+.IP \(bu 2
+global configuration file (defaults to \fB$PREFIX/etc/npmrc\fP; configurable via
+CLI option \fB\-\-globalconfig\fP or environment variable \fB$NPM_CONFIG_GLOBALCONFIG\fP)
+.IP \(bu 2
+npm's built\-in configuration file (\fB/path/to/npm/npmrc\fP)
+
+.RE
+.P
+See npm help npmrc for more details\.
+.SS Default Configs
+.P
+Run \fBnpm config ls \-l\fP to see a set of configuration parameters that are
+internal to npm, and are defaults if nothing else is specified\.
+.SS Shorthands and Other CLI Niceties
+.P
+The following shorthands are parsed on the command\-line:
+.RS 0
+.IP \(bu 2
+\fB\-v\fP: \fB\-\-version\fP
+.IP \(bu 2
+\fB\-h\fP, \fB\-?\fP, \fB\-\-help\fP, \fB\-H\fP: \fB\-\-usage\fP
+.IP \(bu 2
+\fB\-s\fP, \fB\-\-silent\fP: \fB\-\-loglevel silent\fP
+.IP \(bu 2
+\fB\-q\fP, \fB\-\-quiet\fP: \fB\-\-loglevel warn\fP
+.IP \(bu 2
+\fB\-d\fP: \fB\-\-loglevel info\fP
+.IP \(bu 2
+\fB\-dd\fP, \fB\-\-verbose\fP: \fB\-\-loglevel verbose\fP
+.IP \(bu 2
+\fB\-ddd\fP: \fB\-\-loglevel silly\fP
+.IP \(bu 2
+\fB\-g\fP: \fB\-\-global\fP
+.IP \(bu 2
+\fB\-C\fP: \fB\-\-prefix\fP
+.IP \(bu 2
+\fB\-l\fP: \fB\-\-long\fP
+.IP \(bu 2
+\fB\-m\fP: \fB\-\-message\fP
+.IP \(bu 2
+\fB\-p\fP, \fB\-\-porcelain\fP: \fB\-\-parseable\fP
+.IP \(bu 2
+\fB\-reg\fP: \fB\-\-registry\fP
+.IP \(bu 2
+\fB\-f\fP: \fB\-\-force\fP
+.IP \(bu 2
+\fB\-desc\fP: \fB\-\-description\fP
+.IP \(bu 2
+\fB\-S\fP: \fB\-\-save\fP
+.IP \(bu 2
+\fB\-P\fP: \fB\-\-save\-prod\fP
+.IP \(bu 2
+\fB\-D\fP: \fB\-\-save\-dev\fP
+.IP \(bu 2
+\fB\-O\fP: \fB\-\-save\-optional\fP
+.IP \(bu 2
+\fB\-B\fP: \fB\-\-save\-bundle\fP
+.IP \(bu 2
+\fB\-E\fP: \fB\-\-save\-exact\fP
+.IP \(bu 2
+\fB\-y\fP: \fB\-\-yes\fP
+.IP \(bu 2
+\fB\-n\fP: \fB\-\-yes false\fP
+.IP \(bu 2
+\fBll\fP and \fBla\fP commands: \fBls \-\-long\fP
+
+.RE
+.P
+If the specified configuration param resolves unambiguously to a known
+configuration parameter, then it is expanded to that configuration
+parameter\.  For example:
+.P
+.RS 2
+.nf
+npm ls \-\-par
+# same as:
+npm ls \-\-parseable
+.fi
+.RE
+.P
+If multiple single\-character shorthands are strung together, and the
+resulting combination is unambiguously not some other configuration
+param, then it is expanded to its various component pieces\.  For
+example:
+.P
+.RS 2
+.nf
+npm ls \-gpld
+# same as:
+npm ls \-\-global \-\-parseable \-\-long \-\-loglevel info
+.fi
+.RE
+.SS Per\-Package Config Settings
+.P
+When running scripts (see npm help \fBscripts\fP) the package\.json "config"
+keys are overwritten in the environment if there is a config param of
+\fB<name>[@<version>]:<key>\fP\|\.  For example, if the package\.json has
+this:
+.P
+.RS 2
+.nf
+{ "name" : "foo"
+, "config" : { "port" : "8080" }
+, "scripts" : { "start" : "node server\.js" } }
+.fi
+.RE
+.P
+and the server\.js is this:
+.P
+.RS 2
+.nf
+http\.createServer(\.\.\.)\.listen(process\.env\.npm_package_config_port)
+.fi
+.RE
+.P
+then the user could change the behavior by doing:
+.P
+.RS 2
+.nf
+npm config set foo:port 80
+.fi
+.RE
+.P
+See npm help package\.json for more information\.
+.SS Config Settings
+.SS access
+.RS 0
+.IP \(bu 2
+Default: \fBrestricted\fP
+.IP \(bu 2
+Type: Access
+
+.RE
+.P
+When publishing scoped packages, the access level defaults to \fBrestricted\fP\|\.  If
+you want your scoped package to be publicly viewable (and installable) set
+\fB\-\-access=public\fP\|\. The only valid values for \fBaccess\fP are \fBpublic\fP and
+\fBrestricted\fP\|\. Unscoped packages \fIalways\fR have an access level of \fBpublic\fP\|\.
+.SS allow\-same\-version
+.RS 0
+.IP \(bu 2
+Default: false
+.IP \(bu 2
+Type: Boolean
+
+.RE
+.P
+Prevents throwing an error when \fBnpm version\fP is used to set the new version
+to the same value as the current version\.
+.SS always\-auth
+.RS 0
+.IP \(bu 2
+Default: false
+.IP \(bu 2
+Type: Boolean
+
+.RE
+.P
+Force npm to always require authentication when accessing the registry,
+even for \fBGET\fP requests\.
+.SS also
+.RS 0
+.IP \(bu 2
+Default: null
+.IP \(bu 2
+Type: String
+
+.RE
+.P
+When "dev" or "development" and running local \fBnpm shrinkwrap\fP,
+\fBnpm outdated\fP, or \fBnpm update\fP, is an alias for \fB\-\-dev\fP\|\.
+.SS audit
+.RS 0
+.IP \(bu 2
+Default: true
+.IP \(bu 2
+Type: Boolean
+
+.RE
+.P
+When "true" submit audit reports alongside \fBnpm install\fP runs to the default
+registry and all registries configured for scopes\.  See the documentation
+for npm help \fBaudit\fP for details on what is submitted\.
+.SS audit\-level
+.RS 0
+.IP \(bu 2
+Default: \fB"low"\fP
+.IP \(bu 2
+Type: \fB\|'low'\fP, \fB\|'moderate'\fP, \fB\|'high'\fP, \fB\|'critical'\fP
+
+.RE
+.P
+The minimum level of vulnerability for \fBnpm audit\fP to exit with
+a non\-zero exit code\.
+.SS auth\-type
+.RS 0
+.IP \(bu 2
+Default: \fB\|'legacy'\fP
+.IP \(bu 2
+Type: \fB\|'legacy'\fP, \fB\|'sso'\fP, \fB\|'saml'\fP, \fB\|'oauth'\fP
+
+.RE
+.P
+What authentication strategy to use with \fBadduser\fP/\fBlogin\fP\|\.
+.SS before
+.RS 0
+.IP \(bu 2
+Alias: enjoy\-by
+.IP \(bu 2
+Default: null
+.IP \(bu 2
+Type: Date
+
+.RE
+.P
+If passed to \fBnpm install\fP, will rebuild the npm tree such that only versions
+that were available \fBon or before\fR the \fB\-\-before\fP time get installed\.
+If there's no versions available for the current set of direct dependencies, the
+command will error\.
+.P
+If the requested version is a \fBdist\-tag\fP and the given tag does not pass the
+\fB\-\-before\fP filter, the most recent version less than or equal to that tag will
+be used\. For example, \fBfoo@latest\fP might install \fBfoo@1\.2\fP even though \fBlatest\fP
+is \fB2\.0\fP\|\.
+.SS bin\-links
+.RS 0
+.IP \(bu 2
+Default: \fBtrue\fP
+.IP \(bu 2
+Type: Boolean
+
+.RE
+.P
+Tells npm to create symlinks (or \fB\|\.cmd\fP shims on Windows) for package
+executables\.
+.P
+Set to false to have it not do this\.  This can be used to work around
+the fact that some file systems don't support symlinks, even on
+ostensibly Unix systems\.
+.SS browser
+.RS 0
+.IP \(bu 2
+Default: OS X: \fB"open"\fP, Windows: \fB"start"\fP, Others: \fB"xdg\-open"\fP
+.IP \(bu 2
+Type: String
+
+.RE
+.P
+The browser that is called by the \fBnpm docs\fP command to open websites\.
+.SS ca
+.RS 0
+.IP \(bu 2
+Default: The npm CA certificate
+.IP \(bu 2
+Type: String, Array or null
+
+.RE
+.P
+The Certificate Authority signing certificate that is trusted for SSL
+connections to the registry\. Values should be in PEM format (Windows calls it "Base\-64 encoded X\.509 (\.CER)") with newlines
+replaced by the string "\\n"\. For example:
+.P
+.RS 2
+.nf
+ca="\-\-\-\-\-BEGIN CERTIFICATE\-\-\-\-\-\\nXXXX\\nXXXX\\n\-\-\-\-\-END CERTIFICATE\-\-\-\-\-"
+.fi
+.RE
+.P
+Set to \fBnull\fP to only allow "known" registrars, or to a specific CA cert
+to trust only that specific signing authority\.
+.P
+Multiple CAs can be trusted by specifying an array of certificates:
+.P
+.RS 2
+.nf
+ca[]="\.\.\."
+ca[]="\.\.\."
+.fi
+.RE
+.P
+See also the \fBstrict\-ssl\fP config\.
+.SS cafile
+.RS 0
+.IP \(bu 2
+Default: \fBnull\fP
+.IP \(bu 2
+Type: path
+
+.RE
+.P
+A path to a file containing one or multiple Certificate Authority signing
+certificates\. Similar to the \fBca\fP setting, but allows for multiple CA's, as
+well as for the CA information to be stored in a file on disk\.
+.SS cache
+.RS 0
+.IP \(bu 2
+Default: Windows: \fB%AppData%\\npm\-cache\fP, Posix: \fB~/\.npm\fP
+.IP \(bu 2
+Type: path
+
+.RE
+.P
+The location of npm's cache directory\.  See npm help \fBcache\fP
+.SS cache\-lock\-stale
+.RS 0
+.IP \(bu 2
+Default: 60000 (1 minute)
+.IP \(bu 2
+Type: Number
+
+.RE
+.P
+The number of ms before cache folder lockfiles are considered stale\.
+.SS cache\-lock\-retries
+.RS 0
+.IP \(bu 2
+Default: 10
+.IP \(bu 2
+Type: Number
+
+.RE
+.P
+Number of times to retry to acquire a lock on cache folder lockfiles\.
+.SS cache\-lock\-wait
+.RS 0
+.IP \(bu 2
+Default: 10000 (10 seconds)
+.IP \(bu 2
+Type: Number
+
+.RE
+.P
+Number of ms to wait for cache lock files to expire\.
+.SS cache\-max
+.RS 0
+.IP \(bu 2
+Default: Infinity
+.IP \(bu 2
+Type: Number
+
+.RE
+.P
+\fBDEPRECATED\fR: This option has been deprecated in favor of \fB\-\-prefer\-online\fP\|\.
+.P
+\fB\-\-cache\-max=0\fP is an alias for \fB\-\-prefer\-online\fP\|\.
+.SS cache\-min
+.RS 0
+.IP \(bu 2
+Default: 10
+.IP \(bu 2
+Type: Number
+
+.RE
+.P
+\fBDEPRECATED\fR: This option has been deprecated in favor of \fB\-\-prefer\-offline\fP\|\.
+.P
+\fB\-\-cache\-min=9999 (or bigger)\fP is an alias for \fB\-\-prefer\-offline\fP\|\.
+.SS cert
+.RS 0
+.IP \(bu 2
+Default: \fBnull\fP
+.IP \(bu 2
+Type: String
+
+.RE
+.P
+A client certificate to pass when accessing the registry\.  Values should be in
+PEM format (Windows calls it "Base\-64 encoded X\.509 (\.CER)") with newlines replaced by the string "\\n"\. For example:
+.P
+.RS 2
+.nf
+cert="\-\-\-\-\-BEGIN CERTIFICATE\-\-\-\-\-\\nXXXX\\nXXXX\\n\-\-\-\-\-END CERTIFICATE\-\-\-\-\-"
+.fi
+.RE
+.P
+It is \fInot\fR the path to a certificate file (and there is no "certfile" option)\.
+.SS cidr
+.RS 0
+.IP \(bu 2
+Default: \fBnull\fP
+.IP \(bu 2
+Type: String, Array, null
+
+.RE
+.P
+This is a list of CIDR address to be used when configuring limited access tokens with the \fBnpm token create\fP command\.
+.SS color
+.RS 0
+.IP \(bu 2
+Default: true
+.IP \(bu 2
+Type: Boolean or \fB"always"\fP
+
+.RE
+.P
+If false, never shows colors\.  If \fB"always"\fP then always shows colors\.
+If true, then only prints color codes for tty file descriptors\.
+.P
+This option can also be changed using the environment: colors are
+disabled when the environment variable \fBNO_COLOR\fP is set to any value\.
+.SS depth
+.RS 0
+.IP \(bu 2
+Default: Infinity
+.IP \(bu 2
+Type: Number
+
+.RE
+.P
+The depth to go when recursing directories for \fBnpm ls\fP,
+\fBnpm cache ls\fP, and \fBnpm outdated\fP\|\.
+.P
+For \fBnpm outdated\fP, a setting of \fBInfinity\fP will be treated as \fB0\fP
+since that gives more useful information\.  To show the outdated status
+of all packages and dependents, use a large integer value,
+e\.g\., \fBnpm outdated \-\-depth 9999\fP
+.SS description
+.RS 0
+.IP \(bu 2
+Default: true
+.IP \(bu 2
+Type: Boolean
+
+.RE
+.P
+Show the description in \fBnpm search\fP
+.SS dev
+.RS 0
+.IP \(bu 2
+Default: false
+.IP \(bu 2
+Type: Boolean
+
+.RE
+.P
+Install \fBdev\-dependencies\fP along with packages\.
+.SS dry\-run
+.RS 0
+.IP \(bu 2
+Default: false
+.IP \(bu 2
+Type: Boolean
+
+.RE
+.P
+Indicates that you don't want npm to make any changes and that it should
+only report what it would have done\.  This can be passed into any of the
+commands that modify your local installation, eg, \fBinstall\fP, \fBupdate\fP,
+\fBdedupe\fP, \fBuninstall\fP\|\.  This is NOT currently honored by some network related
+commands, eg \fBdist\-tags\fP, \fBowner\fP, etc\.
+.SS editor
+.RS 0
+.IP \(bu 2
+Default: \fBEDITOR\fP environment variable if set, or \fB"vi"\fP on Posix,
+or \fB"notepad"\fP on Windows\.
+.IP \(bu 2
+Type: path
+
+.RE
+.P
+The command to run for \fBnpm edit\fP or \fBnpm config edit\fP\|\.
+.SS engine\-strict
+.RS 0
+.IP \(bu 2
+Default: false
+.IP \(bu 2
+Type: Boolean
+
+.RE
+.P
+If set to true, then npm will stubbornly refuse to install (or even
+consider installing) any package that claims to not be compatible with
+the current Node\.js version\.
+.SS force
+.RS 0
+.IP \(bu 2
+Default: false
+.IP \(bu 2
+Type: Boolean
+
+.RE
+.P
+Makes various commands more forceful\.
+.RS 0
+.IP \(bu 2
+lifecycle script failure does not block progress\.
+.IP \(bu 2
+publishing clobbers previously published versions\.
+.IP \(bu 2
+skips cache when requesting from the registry\.
+.IP \(bu 2
+prevents checks against clobbering non\-npm files\.
+
+.RE
+.SS format\-package\-lock
+.RS 0
+.IP \(bu 2
+Default: true
+.IP \(bu 2
+Type: Boolean
+
+.RE
+.P
+Format \fBpackage\-lock\.json\fP or \fBnpm\-shrinkwrap\.json\fP as a human readable file\.
+.SS fetch\-retries
+.RS 0
+.IP \(bu 2
+Default: 2
+.IP \(bu 2
+Type: Number
+
+.RE
+.P
+The "retries" config for the \fBretry\fP module to use when fetching
+packages from the registry\.
+.SS fetch\-retry\-factor
+.RS 0
+.IP \(bu 2
+Default: 10
+.IP \(bu 2
+Type: Number
+
+.RE
+.P
+The "factor" config for the \fBretry\fP module to use when fetching
+packages\.
+.SS fetch\-retry\-mintimeout
+.RS 0
+.IP \(bu 2
+Default: 10000 (10 seconds)
+.IP \(bu 2
+Type: Number
+
+.RE
+.P
+The "minTimeout" config for the \fBretry\fP module to use when fetching
+packages\.
+.SS fetch\-retry\-maxtimeout
+.RS 0
+.IP \(bu 2
+Default: 60000 (1 minute)
+.IP \(bu 2
+Type: Number
+
+.RE
+.P
+The "maxTimeout" config for the \fBretry\fP module to use when fetching
+packages\.
+.SS fund
+.RS 0
+.IP \(bu 2
+Default: true
+.IP \(bu 2
+Type: Boolean
+
+.RE
+.P
+When "true" displays the message at the end of each \fBnpm install\fP
+aknowledging the number of dependencies looking for funding\.
+See npm help \fBfund\fP for details\.
+.SS git
+.RS 0
+.IP \(bu 2
+Default: \fB"git"\fP
+.IP \(bu 2
+Type: String
+
+.RE
+.P
+The command to use for git commands\.  If git is installed on the
+computer, but is not in the \fBPATH\fP, then set this to the full path to
+the git binary\.
+.SS git\-tag\-version
+.RS 0
+.IP \(bu 2
+Default: \fBtrue\fP
+.IP \(bu 2
+Type: Boolean
+
+.RE
+.P
+Tag the commit when using the \fBnpm version\fP command\.
+.SS commit\-hooks
+.RS 0
+.IP \(bu 2
+Default: \fBtrue\fP
+.IP \(bu 2
+Type: Boolean
+
+.RE
+.P
+Run git commit hooks when using the \fBnpm version\fP command\.
+.SS global
+.RS 0
+.IP \(bu 2
+Default: false
+.IP \(bu 2
+Type: Boolean
+
+.RE
+.P
+Operates in "global" mode, so that packages are installed into the
+\fBprefix\fP folder instead of the current working directory\.  See
+npm help folders for more on the differences in behavior\.
+.RS 0
+.IP \(bu 2
+packages are installed into the \fB{prefix}/lib/node_modules\fP folder, instead of the
+current working directory\.
+.IP \(bu 2
+bin files are linked to \fB{prefix}/bin\fP
+.IP \(bu 2
+man pages are linked to \fB{prefix}/share/man\fP
+
+.RE
+.SS globalconfig
+.RS 0
+.IP \(bu 2
+Default: {prefix}/etc/npmrc
+.IP \(bu 2
+Type: path
+
+.RE
+.P
+The config file to read for global config options\.
+.SS global\-style
+.RS 0
+.IP \(bu 2
+Default: false
+.IP \(bu 2
+Type: Boolean
+
+.RE
+.P
+Causes npm to install the package into your local \fBnode_modules\fP folder with
+the same layout it uses with the global \fBnode_modules\fP folder\.  Only your
+direct dependencies will show in \fBnode_modules\fP and everything they depend
+on will be flattened in their \fBnode_modules\fP folders\.  This obviously will
+eliminate some deduping\. If used with \fBlegacy\-bundling\fP, \fBlegacy\-bundling\fP will be
+preferred\.
+.SS group
+.RS 0
+.IP \(bu 2
+Default: GID of the current process
+.IP \(bu 2
+Type: String or Number
+
+.RE
+.P
+The group to use when running package scripts in global mode as the root
+user\.
+.SS heading
+.RS 0
+.IP \(bu 2
+Default: \fB"npm"\fP
+.IP \(bu 2
+Type: String
+
+.RE
+.P
+The string that starts all the debugging log output\.
+.SS https\-proxy
+.RS 0
+.IP \(bu 2
+Default: null
+.IP \(bu 2
+Type: url
+
+.RE
+.P
+A proxy to use for outgoing https requests\. If the \fBHTTPS_PROXY\fP or
+\fBhttps_proxy\fP or \fBHTTP_PROXY\fP or \fBhttp_proxy\fP environment variables are set,
+proxy settings will be honored by the underlying \fBrequest\fP library\.
+.SS if\-present
+.RS 0
+.IP \(bu 2
+Default: false
+.IP \(bu 2
+Type: Boolean
+
+.RE
+.P
+If true, npm will not exit with an error code when \fBrun\-script\fP is invoked for
+a script that isn't defined in the \fBscripts\fP section of \fBpackage\.json\fP\|\. This
+option can be used when it's desirable to optionally run a script when it's
+present and fail if the script fails\. This is useful, for example, when running
+scripts that may only apply for some builds in an otherwise generic CI setup\.
+.SS ignore\-prepublish
+.RS 0
+.IP \(bu 2
+Default: false
+.IP \(bu 2
+Type: Boolean
+
+.RE
+.P
+If true, npm will not run \fBprepublish\fP scripts\.
+.SS ignore\-scripts
+.RS 0
+.IP \(bu 2
+Default: false
+.IP \(bu 2
+Type: Boolean
+
+.RE
+.P
+If true, npm does not run scripts specified in package\.json files\.
+.SS init\-module
+.RS 0
+.IP \(bu 2
+Default: ~/\.npm\-init\.js
+.IP \(bu 2
+Type: path
+
+.RE
+.P
+A module that will be loaded by the \fBnpm init\fP command\.  See the
+documentation for the
+init\-package\-json \fIhttps://github\.com/isaacs/init\-package\-json\fR module
+for more information, or npm help init\.
+.SS init\-author\-name
+.RS 0
+.IP \(bu 2
+Default: ""
+.IP \(bu 2
+Type: String
+
+.RE
+.P
+The value \fBnpm init\fP should use by default for the package author's name\.
+.SS init\-author\-email
+.RS 0
+.IP \(bu 2
+Default: ""
+.IP \(bu 2
+Type: String
+
+.RE
+.P
+The value \fBnpm init\fP should use by default for the package author's email\.
+.SS init\-author\-url
+.RS 0
+.IP \(bu 2
+Default: ""
+.IP \(bu 2
+Type: String
+
+.RE
+.P
+The value \fBnpm init\fP should use by default for the package author's homepage\.
+.SS init\-license
+.RS 0
+.IP \(bu 2
+Default: "ISC"
+.IP \(bu 2
+Type: String
+
+.RE
+.P
+The value \fBnpm init\fP should use by default for the package license\.
+.SS init\-version
+.RS 0
+.IP \(bu 2
+Default: "1\.0\.0"
+.IP \(bu 2
+Type: semver
+
+.RE
+.P
+The value that \fBnpm init\fP should use by default for the package
+version number, if not already set in package\.json\.
+.SS json
+.RS 0
+.IP \(bu 2
+Default: false
+.IP \(bu 2
+Type: Boolean
+
+.RE
+.P
+Whether or not to output JSON data, rather than the normal output\.
+.P
+This feature is currently experimental, and the output data structures for many
+commands is either not implemented in JSON yet, or subject to change\.  Only the
+output from \fBnpm ls \-\-json\fP and \fBnpm search \-\-json\fP are currently valid\.
+.SS key
+.RS 0
+.IP \(bu 2
+Default: \fBnull\fP
+.IP \(bu 2
+Type: String
+
+.RE
+.P
+A client key to pass when accessing the registry\.  Values should be in PEM
+format with newlines replaced by the string "\\n"\. For example:
+.P
+.RS 2
+.nf
+key="\-\-\-\-\-BEGIN PRIVATE KEY\-\-\-\-\-\\nXXXX\\nXXXX\\n\-\-\-\-\-END PRIVATE KEY\-\-\-\-\-"
+.fi
+.RE
 .P
 It is \fInot\fR the path to a key file (and there is no "keyfile" option)\.
 .SS legacy\-bundling