diff options
| author | Ruy Adorno <ruyadorno@hotmail.com> | 2019-11-05 14:55:08 -0500 |
|---|---|---|
| committer | Rich Trott <rtrott@gmail.com> | 2019-11-09 20:13:43 -0800 |
| commit | 4b97c3addb246274cd7e8432edd537e0bdf60b63 (patch) | |
| tree | 9f859239c3b38b04ddc58ee736bf6b2caf6008a5 /deps/npm/man/man1 | |
| parent | 5f9794ea9aaaf5597974a65460e1f3069f68475f (diff) | |
| download | android-node-v8-4b97c3addb246274cd7e8432edd537e0bdf60b63.tar.gz android-node-v8-4b97c3addb246274cd7e8432edd537e0bdf60b63.tar.bz2 android-node-v8-4b97c3addb246274cd7e8432edd537e0bdf60b63.zip | |
deps: update npm to 6.13.0
PR-URL: https://github.com/nodejs/node/pull/30271
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Diffstat (limited to 'deps/npm/man/man1')
60 files changed, 784 insertions, 877 deletions
diff --git a/deps/npm/man/man1/npm-README.1 b/deps/npm/man/man1/npm-README.1 index 1a34494860..73e841ba88 100644 --- a/deps/npm/man/man1/npm-README.1 +++ b/deps/npm/man/man1/npm-README.1 @@ -1,6 +1,6 @@ -.TH "NPM" "1" "October 2019" "" "" +.TH "NPM" "" "November 2019" "" "" .SH "NAME" -\fBnpm\fR \- a JavaScript package manager +\fBnpm\fR .P Build Status \fIhttps://img\.shields\.io/travis/npm/cli/latest\.svg\fR \fIhttps://travis\-ci\.org/npm/cli\fR .SH SYNOPSIS @@ -168,8 +168,5 @@ doubt tell you to put the output in a gist or email\. npm help npm .IP \(bu 2 npm help help -.IP \(bu 2 -npm help 7 index .RE - diff --git a/deps/npm/man/man1/npm-access.1 b/deps/npm/man/man1/npm-access.1 index 16dcab9519..8bd724d066 100644 --- a/deps/npm/man/man1/npm-access.1 +++ b/deps/npm/man/man1/npm-access.1 @@ -1,7 +1,8 @@ -.TH "NPM\-ACCESS" "1" "October 2019" "" "" +.TH "NPM\-ACCESS" "" "November 2019" "" "" .SH "NAME" -\fBnpm-access\fR \- Set access level on published packages -.SH SYNOPSIS +\fBnpm-access\fR +.SH Set access level on published packages +.SS Synopsis .P .RS 2 .nf @@ -19,7 +20,7 @@ npm access ls\-collaborators [<package> [<user>]] npm access edit [<package>] .fi .RE -.SH DESCRIPTION +.SS Description .P Used to set access controls on private packages\. .P @@ -53,7 +54,7 @@ edit: Set the access privileges for a package at once using \fB$EDITOR\fP\|\. .RE -.SH DETAILS +.SS Details .P \fBnpm access\fP always operates directly on the current registry, configurable from the command line using \fB\-\-registry=<registry url>\fP\|\. @@ -84,18 +85,17 @@ with an HTTP 402 status code (logically enough), unless you use \fB\-\-access=public\fP\|\. .P Management of teams and team memberships is done with the \fBnpm team\fP command\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 \fBlibnpmaccess\fP \fIhttps://npm\.im/libnpmaccess\fR .IP \(bu 2 -npm help team +npm help npm\-team .IP \(bu 2 -npm help publish +npm help npm\-publish .IP \(bu 2 -npm help 7 config +npm help npm\-config .IP \(bu 2 -npm help 7 registry +npm help registry .RE - diff --git a/deps/npm/man/man1/npm-adduser.1 b/deps/npm/man/man1/npm-adduser.1 index 5ea0f27ee4..f8c75cc715 100644 --- a/deps/npm/man/man1/npm-adduser.1 +++ b/deps/npm/man/man1/npm-adduser.1 @@ -1,7 +1,8 @@ -.TH "NPM\-ADDUSER" "1" "October 2019" "" "" +.TH "NPM\-ADDUSER" "" "November 2019" "" "" .SH "NAME" -\fBnpm-adduser\fR \- Add a registry user account -.SH SYNOPSIS +\fBnpm-adduser\fR +.SH Add a registry user account +.SS Synopsis .P .RS 2 .nf @@ -10,11 +11,11 @@ npm adduser [\-\-registry=url] [\-\-scope=@orgname] [\-\-always\-auth] [\-\-auth aliases: login, add\-user .fi .RE -.SH DESCRIPTION +.SS Description .P Create or verify a user named \fB<username>\fP in the specified registry, and save the credentials to the \fB\|\.npmrc\fP file\. If no registry is specified, -the default registry will be used (see npm help 7 \fBnpm\-config\fP)\. +the default registry will be used (see \fBnpm\-config\fP \fInpm\-config)\fR\|\. .P The username, password, and email are read in from prompts\. .P @@ -28,25 +29,25 @@ the username, password and email address must all match with your existing record\. .P \fBnpm login\fP is an alias to \fBadduser\fP and behaves exactly the same way\. -.SH CONFIGURATION +.SS Configuration .SS registry .P Default: https://registry\.npmjs\.org/ .P The base URL of the npm package registry\. If \fBscope\fP is also specified, this registry will only be used for packages with that scope\. \fBscope\fP defaults -to the scope of the project directory you're currently in, if any\. See npm help 7 \fBnpm\-scope\fP\|\. +to the scope of the project directory you're currently in, if any\. See \fBnpm\-scope\fP \fI/docs/using\-npm/scope\fR\|\. .SS scope .P Default: none .P If specified, the user and login credentials given will be associated -with the specified scope\. See npm help 7 \fBnpm\-scope\fP\|\. You can use both at the same time, +with the specified scope\. See \fBnpm\-scope\fP \fI/docs/using\-npm/scope\fR\|\. You can use both at the same time, e\.g\. .P .RS 2 .nf -npm adduser \-\-registry=http://myregistry\.example\.com \-\-scope=@myco + npm adduser \-\-registry=http://myregistry\.example\.com \-\-scope=@myco .fi .RE .P @@ -62,14 +63,14 @@ registries\. Can be used with \fB\-\-registry\fP and / or \fB\-\-scope\fP, e\.g\ .P .RS 2 .nf -npm adduser \-\-registry=http://private\-registry\.example\.com \-\-always\-auth + npm adduser \-\-registry=http://private\-registry\.example\.com \-\-always\-auth .fi .RE .P This will ensure that all requests to that registry (including for tarballs) include an authorization header\. This setting may be necessary for use with private registries where metadata and package tarballs are stored on hosts with -different hostnames\. See \fBalways\-auth\fP in npm help 7 \fBnpm\-config\fP for more details on +different hostnames\. See \fBalways\-auth\fP in \fBnpm\-config\fP \fI/docs/using\-npm/config\fR for more details on always\-auth\. Registry\-specific configuration of \fBalways\-auth\fP takes precedence over any global configuration\. .SS auth\-type @@ -84,20 +85,17 @@ Type: \fB\|'legacy'\fP, \fB\|'sso'\fP, \fB\|'saml'\fP, \fB\|'oauth'\fP What authentication strategy to use with \fBadduser\fP/\fBlogin\fP\|\. Some npm registries (for example, npmE) might support alternative auth strategies besides classic username/password entry in legacy npm\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help 7 registry +npm help registry .IP \(bu 2 -npm help config +npm help npm\-config .IP \(bu 2 -npm help 7 config +npm help npmrc .IP \(bu 2 -npm help 5 npmrc +npm help npm\-owner .IP \(bu 2 -npm help owner -.IP \(bu 2 -npm help whoami +npm help npm\-whoami .RE - diff --git a/deps/npm/man/man1/npm-audit.1 b/deps/npm/man/man1/npm-audit.1 index 4f5d8a6980..9641530e40 100644 --- a/deps/npm/man/man1/npm-audit.1 +++ b/deps/npm/man/man1/npm-audit.1 @@ -1,7 +1,8 @@ -.TH "NPM\-AUDIT" "1" "October 2019" "" "" +.TH "NPM\-AUDIT" "" "November 2019" "" "" .SH "NAME" -\fBnpm-audit\fR \- Run a security audit -.SH SYNOPSIS +\fBnpm-audit\fR +.SH Run a security audit +.SS Synopsis .P .RS 2 .nf @@ -11,7 +12,7 @@ npm audit fix [\-\-force|\-\-package\-lock\-only|\-\-dry\-run] common options: [\-\-production] [\-\-only=(dev|prod)] .fi .RE -.SH EXAMPLES +.SS Examples .P Scan your project for vulnerabilities and automatically install any compatible updates to vulnerable dependencies: @@ -99,7 +100,7 @@ Fail an audit only if the results include a vulnerability with a level of modera $ npm audit \-\-audit\-level=moderate .fi .RE -.SH DESCRIPTION +.SS Description .P The audit command submits a description of the dependencies configured in your project to your default registry and asks for a report of known @@ -119,7 +120,7 @@ is found\. It may be useful in CI environments to include the \fB\-\-audit\-leve to specify the minimum vulnerability level that will cause the command to fail\. This option does not filter the report output, it simply changes the command's failure threshold\. -.SH CONTENT SUBMITTED +.SS Content Submitted .RS 0 .IP \(bu 2 npm_version @@ -133,7 +134,7 @@ node_env A scrubbed version of your package\-lock\.json or npm\-shrinkwrap\.json .RE -.SS SCRUBBING +.SS Scrubbing .P In order to ensure that potentially sensitive information is not included in the audit data bundle, some dependencies may have their names (and sometimes @@ -155,19 +156,19 @@ All local directory and tarball dependencies have their names and specifiers scr The non\-reversible identifiers are a sha256 of a session\-specific UUID and the value being replaced, ensuring a consistent value within the payload that is different between runs\. -.SH EXIT CODE +.SS Exit Code .P The \fBnpm audit\fP command will exit with a 0 exit code if no vulnerabilities were found\. .P If vulnerabilities were found the exit code will depend on the \fBaudit\-level\fP configuration setting\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help install +npm help npm\-install .IP \(bu 2 -npm help 5 package\-locks +npm help package\-locks .IP \(bu 2 -npm help 7 config +npm help config .RE diff --git a/deps/npm/man/man1/npm-bin.1 b/deps/npm/man/man1/npm-bin.1 index 3ffed54b37..157fdda28c 100644 --- a/deps/npm/man/man1/npm-bin.1 +++ b/deps/npm/man/man1/npm-bin.1 @@ -1,30 +1,28 @@ -.TH "NPM\-BIN" "1" "October 2019" "" "" +.TH "NPM\-BIN" "" "November 2019" "" "" .SH "NAME" -\fBnpm-bin\fR \- Display npm bin folder -.SH SYNOPSIS +\fBnpm-bin\fR +.SH Display npm bin folder +.SS Synopsis .P .RS 2 .nf npm bin [\-g|\-\-global] .fi .RE -.SH DESCRIPTION +.SS Description .P Print the folder where npm will install executables\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help prefix +npm help npm\-prefix .IP \(bu 2 -npm help root +npm help npm\-root .IP \(bu 2 -npm help 5 folders +npm help folders .IP \(bu 2 -npm help config +npm help npm\-config .IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc +npm help npmrc .RE - diff --git a/deps/npm/man/man1/npm-bugs.1 b/deps/npm/man/man1/npm-bugs.1 index ad72639c7f..8a11be5d79 100644 --- a/deps/npm/man/man1/npm-bugs.1 +++ b/deps/npm/man/man1/npm-bugs.1 @@ -1,7 +1,8 @@ -.TH "NPM\-BUGS" "1" "October 2019" "" "" +.TH "NPM\-BUGS" "" "November 2019" "" "" .SH "NAME" -\fBnpm-bugs\fR \- Bugs for a package in a web browser maybe -.SH SYNOPSIS +\fBnpm-bugs\fR +.SH Bugs for a package in a web browser maybe +.SS Synopsis .P .RS 2 .nf @@ -10,13 +11,13 @@ npm bugs [<pkgname>] aliases: issues .fi .RE -.SH DESCRIPTION +.SS Description .P This command tries to guess at the likely location of a package's bug tracker URL, and then tries to open it using the \fB\-\-browser\fP config param\. If no package name is provided, it will search for a \fBpackage\.json\fP in the current folder and use the \fBname\fP property\. -.SH CONFIGURATION +.SS Configuration .SS browser .RS 0 .IP \(bu 2 @@ -37,24 +38,21 @@ Type: url .RE .P The base URL of the npm package registry\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help docs +npm help npm\-docs .IP \(bu 2 -npm help view +npm help npm\-view .IP \(bu 2 -npm help publish +npm help npm\-publish .IP \(bu 2 -npm help 7 registry +npm help registry .IP \(bu 2 -npm help config +npm help npm\-config .IP \(bu 2 -npm help 7 config +npm help npmrc .IP \(bu 2 -npm help 5 npmrc -.IP \(bu 2 -npm help 5 package\.json +npm help package\-json .RE - diff --git a/deps/npm/man/man1/npm-build.1 b/deps/npm/man/man1/npm-build.1 index 7f0cd77aaa..f3341bfbed 100644 --- a/deps/npm/man/man1/npm-build.1 +++ b/deps/npm/man/man1/npm-build.1 @@ -1,7 +1,8 @@ -.TH "NPM\-BUILD" "1" "October 2019" "" "" +.TH "NPM\-BUILD" "" "November 2019" "" "" .SH "NAME" -\fBnpm-build\fR \- Build a package -.SH SYNOPSIS +\fBnpm-build\fR +.SH Build a package +.SS Synopsis .P .RS 2 .nf @@ -14,7 +15,7 @@ npm build [<package\-folder>] A folder containing a \fBpackage\.json\fP file in its root\. .RE -.SH DESCRIPTION +.SS Description .P This is the plumbing command called by \fBnpm link\fP and \fBnpm install\fP\|\. .P @@ -23,19 +24,18 @@ directly, run: .P .RS 2 .nf -npm run\-script build + npm run\-script build .fi .RE -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help install +npm help npm\-install .IP \(bu 2 -npm help link +npm help npm\-link .IP \(bu 2 -npm help 7 scripts +npm help scripts .IP \(bu 2 -npm help 5 package\.json +npm help package\-json .RE - diff --git a/deps/npm/man/man1/npm-bundle.1 b/deps/npm/man/man1/npm-bundle.1 index c1044226e6..89a22d5a5e 100644 --- a/deps/npm/man/man1/npm-bundle.1 +++ b/deps/npm/man/man1/npm-bundle.1 @@ -1,17 +1,17 @@ -.TH "NPM\-BUNDLE" "1" "October 2019" "" "" +.TH "NPM\-BUNDLE" "" "November 2019" "" "" .SH "NAME" -\fBnpm-bundle\fR \- REMOVED -.SH DESCRIPTION +\fBnpm-bundle\fR +.SH REMOVED +.SS Description .P The \fBnpm bundle\fP command has been removed in 1\.0, for the simple reason that it is no longer necessary, as the default behavior is now to install packages into the local space\. .P Just use \fBnpm install\fP now to do what \fBnpm bundle\fP used to do\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help install +npm help npm\-install .RE - diff --git a/deps/npm/man/man1/npm-cache.1 b/deps/npm/man/man1/npm-cache.1 index 3e5f7ad2e9..2a54d573c7 100644 --- a/deps/npm/man/man1/npm-cache.1 +++ b/deps/npm/man/man1/npm-cache.1 @@ -1,7 +1,8 @@ -.TH "NPM\-CACHE" "1" "October 2019" "" "" +.TH "NPM\-CACHE" "" "November 2019" "" "" .SH "NAME" -\fBnpm-cache\fR \- Manipulates packages cache -.SH SYNOPSIS +\fBnpm-cache\fR +.SH Manipulates packages cache +.SS Synopsis .P .RS 2 .nf @@ -16,7 +17,7 @@ aliases: npm cache clear, npm cache rm npm cache verify .fi .RE -.SH DESCRIPTION +.SS Description .P Used to add, list, or clean the npm cache folder\. .RS 0 @@ -34,7 +35,7 @@ Verify the contents of the cache folder, garbage collecting any unneeded data, and verifying the integrity of the cache index and all cached data\. .RE -.SH DETAILS +.SS Details .P npm stores cache data in an opaque directory within the configured \fBcache\fP, named \fB_cacache\fP\|\. This directory is a \fBcacache\fP\-based content\-addressable cache @@ -55,7 +56,7 @@ directly\. .P npm will not remove data by itself: the cache will grow as new packages are installed\. -.SH A NOTE ABOUT THE CACHE'S DESIGN +.SS A note about the cache's design .P The npm cache is strictly a cache: it should not be relied upon as a persistent and reliable data store for package data\. npm makes no guarantee that a @@ -65,32 +66,29 @@ if it does return data, that data will be exactly the data that was inserted\. .P To run an offline verification of existing cache contents, use \fBnpm cache verify\fP\|\. -.SH CONFIGURATION +.SS Configuration .SS cache .P Default: \fB~/\.npm\fP on Posix, or \fB%AppData%/npm\-cache\fP on Windows\. .P The root cache folder\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help 5 folders +npm help folders .IP \(bu 2 -npm help config +npm help npm\-config .IP \(bu 2 -npm help 7 config +npm help npmrc .IP \(bu 2 -npm help 5 npmrc +npm help npm\-install .IP \(bu 2 -npm help install +npm help npm\-publish .IP \(bu 2 -npm help publish -.IP \(bu 2 -npm help pack +npm help npm\-pack .IP \(bu 2 https://npm\.im/cacache .IP \(bu 2 https://npm\.im/pacote .RE - diff --git a/deps/npm/man/man1/npm-ci.1 b/deps/npm/man/man1/npm-ci.1 index b0bf8dbeed..6f93d0bc7d 100644 --- a/deps/npm/man/man1/npm-ci.1 +++ b/deps/npm/man/man1/npm-ci.1 @@ -1,14 +1,15 @@ -.TH "NPM\-CI" "1" "October 2019" "" "" +.TH "NPM\-CI" "" "November 2019" "" "" .SH "NAME" -\fBnpm-ci\fR \- Install a project with a clean slate -.SH SYNOPSIS +\fBnpm-ci\fR +.SH Install a project with a clean slate +.SS Synopsis .P .RS 2 .nf npm ci .fi .RE -.SH EXAMPLE +.SS Example .P Make sure you have a package\-lock and an up\-to\-date install: .P @@ -43,9 +44,9 @@ cache: \- "$HOME/\.npm" .fi .RE -.SH DESCRIPTION +.SS Description .P -This command is similar to npm help \fBnpm\-install\fP, except it's meant to be used in +This command is similar to \fBnpm\-install\fP \fInpm\-install\fR, except it's meant to be used in automated environments such as test platforms, continuous integration, and deployment \-\- or any situation where you want to make sure you're doing a clean install of your dependencies\. It can be significantly faster than a regular npm @@ -67,11 +68,11 @@ If a \fBnode_modules\fP is already present, it will be automatically removed bef It will never write to \fBpackage\.json\fP or any of the package\-locks: installs are essentially frozen\. .RE -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help install +npm help npm\-install .IP \(bu 2 -npm help 5 package\-locks +npm help package\-locks .RE diff --git a/deps/npm/man/man1/npm-completion.1 b/deps/npm/man/man1/npm-completion.1 index e864a09741..6e0f840564 100644 --- a/deps/npm/man/man1/npm-completion.1 +++ b/deps/npm/man/man1/npm-completion.1 @@ -1,14 +1,15 @@ -.TH "NPM\-COMPLETION" "1" "October 2019" "" "" +.TH "NPM\-COMPLETION" "" "November 2019" "" "" .SH "NAME" -\fBnpm-completion\fR \- Tab Completion for npm -.SH SYNOPSIS +\fBnpm-completion\fR +.SH Tab Completion for npm +.SS Synopsis .P .RS 2 .nf source <(npm completion) .fi .RE -.SH DESCRIPTION +.SS Description .P Enables tab\-completion in all npm commands\. .P @@ -32,12 +33,11 @@ that file for you\. When \fBCOMP_CWORD\fP, \fBCOMP_LINE\fP, and \fBCOMP_POINT\fP are defined in the environment, \fBnpm completion\fP acts in "plumbing mode", and outputs completions based on the arguments\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help 7 developers +npm help developers .IP \(bu 2 npm help npm .RE - diff --git a/deps/npm/man/man1/npm-config.1 b/deps/npm/man/man1/npm-config.1 index 4c6b59a163..016e8c265a 100644 --- a/deps/npm/man/man1/npm-config.1 +++ b/deps/npm/man/man1/npm-config.1 @@ -1,7 +1,8 @@ -.TH "NPM\-CONFIG" "1" "October 2019" "" "" +.TH "NPM\-CONFIG" "" "November 2019" "" "" .SH "NAME" -\fBnpm-config\fR \- Manage the npm configuration files -.SH SYNOPSIS +\fBnpm-config\fR +.SH Manage the npm configuration files +.SS Synopsis .P .RS 2 .nf @@ -16,19 +17,19 @@ npm set <key> <value> [\-g|\-\-global] aliases: c .fi .RE -.SH DESCRIPTION +.SS Description .P npm gets its config settings from the command line, environment variables, \fBnpmrc\fP files, and in some cases, the \fBpackage\.json\fP file\. .P -See npm help 5 npmrc for more information about the npmrc files\. +See npmrc \fI/docs/configuring\-npm/npmrc\fR for more information about the npmrc files\. .P -See npm help 7 \fBnpm\-config\fP for a more thorough discussion of the mechanisms +See config \fI/docs/using\-npm/config\fR for a more thorough discussion of the mechanisms involved\. .P The \fBnpm config\fP command can be used to update and edit the contents of the user and global npmrc files\. -.SH Sub\-commands +.SS Sub\-commands .P Config supports the following sub\-commands: .SS set @@ -80,18 +81,17 @@ npm config edit .P Opens the config file in an editor\. Use the \fB\-\-global\fP flag to edit the global config\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help 5 folders +npm help folders .IP \(bu 2 -npm help 7 config +npm help npm\-config .IP \(bu 2 -npm help 5 package\.json +npm help package\-json .IP \(bu 2 -npm help 5 npmrc +npm help npmrc .IP \(bu 2 npm help npm .RE - diff --git a/deps/npm/man/man1/npm-dedupe.1 b/deps/npm/man/man1/npm-dedupe.1 index 6104c08692..7795f39652 100644 --- a/deps/npm/man/man1/npm-dedupe.1 +++ b/deps/npm/man/man1/npm-dedupe.1 @@ -1,7 +1,8 @@ -.TH "NPM\-DEDUPE" "1" "October 2019" "" "" +.TH "NPM\-DEDUPE" "" "November 2019" "" "" .SH "NAME" -\fBnpm-dedupe\fR \- Reduce duplication -.SH SYNOPSIS +\fBnpm-dedupe\fR +.SH Reduce duplication +.SS Synopsis .P .RS 2 .nf @@ -11,7 +12,7 @@ npm ddp aliases: find\-dupes, ddp .fi .RE -.SH DESCRIPTION +.SS Description .P Searches the local package tree and attempts to simplify the overall structure by moving dependencies further up the tree, where they can @@ -29,7 +30,7 @@ a .fi .RE .P -In this case, npm help \fBnpm\-dedupe\fP will transform the tree to: +In this case, \fBnpm\-dedupe\fP will transform the tree to: .P .RS 2 .nf @@ -58,14 +59,13 @@ Modules .P Note that this operation transforms the dependency tree, but will never result in new modules being installed\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help ls +npm help npm\-ls .IP \(bu 2 -npm help update +npm help npm\-update .IP \(bu 2 -npm help install +npm help npm\-install .RE - diff --git a/deps/npm/man/man1/npm-deprecate.1 b/deps/npm/man/man1/npm-deprecate.1 index 9fd7e1582c..b010c33447 100644 --- a/deps/npm/man/man1/npm-deprecate.1 +++ b/deps/npm/man/man1/npm-deprecate.1 @@ -1,14 +1,15 @@ -.TH "NPM\-DEPRECATE" "1" "October 2019" "" "" +.TH "NPM\-DEPRECATE" "" "November 2019" "" "" .SH "NAME" -\fBnpm-deprecate\fR \- Deprecate a version of a package -.SH SYNOPSIS +\fBnpm-deprecate\fR +.SH Deprecate a version of a package +.SS Synopsis .P .RS 2 .nf npm deprecate <pkg>[@<version>] <message> .fi .RE -.SH DESCRIPTION +.SS Description .P This command will update the npm registry entry for a package, providing a deprecation warning to all who attempt to install it\. @@ -28,12 +29,11 @@ Note that you must be the package owner to deprecate something\. See the To un\-deprecate a package, specify an empty string (\fB""\fP) for the \fBmessage\fP argument\. Note that you must use double quotes with no space between them to format an empty string\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help publish +npm help npm\-publish .IP \(bu 2 -npm help 7 registry +npm help registry .RE - diff --git a/deps/npm/man/man1/npm-dist-tag.1 b/deps/npm/man/man1/npm-dist-tag.1 index 9880de7cde..0403e8bf67 100644 --- a/deps/npm/man/man1/npm-dist-tag.1 +++ b/deps/npm/man/man1/npm-dist-tag.1 @@ -1,7 +1,8 @@ -.TH "NPM\-DIST\-TAG" "1" "October 2019" "" "" +.TH "NPM\-DIST\-TAG" "" "November 2019" "" "" .SH "NAME" -\fBnpm-dist-tag\fR \- Modify package distribution tags -.SH SYNOPSIS +\fBnpm-dist-tag\fR +.SH Modify package distribution tags +.SS Synopsis .P .RS 2 .nf @@ -12,7 +13,7 @@ npm dist\-tag ls [<pkg>] aliases: dist\-tags .fi .RE -.SH DESCRIPTION +.SS Description .P Add, remove, and enumerate distribution tags on a package: .RS 0 @@ -28,8 +29,7 @@ Clear a tag that is no longer in use from the package\. .IP \(bu 2 ls: Show all of the dist\-tags for a package, defaulting to the package in -the current prefix\. -This is the default action if none is specified\. +the current prefix\. This is the default action if none is specified\. .RE .P @@ -57,7 +57,7 @@ Publishing a package sets the \fBlatest\fP tag to the published version unless t .P By default, \fBnpm install <pkg>\fP (without any \fB@<version>\fP or \fB@<tag>\fP specifier) installs the \fBlatest\fP tag\. -.SH PURPOSE +.SS Purpose .P Tags can be used to provide an alias instead of version numbers\. .P @@ -75,7 +75,7 @@ The \fBnext\fP tag is used by some projects to identify the upcoming version\. .P By default, other than \fBlatest\fP, no tag has any special significance to npm itself\. -.SH CAVEATS +.SS Caveats .P This command used to be known as \fBnpm tag\fP, which only created new tags, and so had a different syntax\. @@ -89,22 +89,19 @@ example, \fBv1\.4\fP cannot be used as a tag, because it is interpreted by semve .P The simplest way to avoid semver problems with tags is to use tags that do not begin with a number or the letter \fBv\fP\|\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help publish +npm help npm\-publish .IP \(bu 2 -npm help install +npm help npm\-install .IP \(bu 2 -npm help dedupe +npm help npm\-dedupe .IP \(bu 2 -npm help 7 registry +npm help registry .IP \(bu 2 -npm help config +npm help npm\-config .IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc +npm help npmrc .RE - diff --git a/deps/npm/man/man1/npm-docs.1 b/deps/npm/man/man1/npm-docs.1 index 49ab61870b..09c786b72e 100644 --- a/deps/npm/man/man1/npm-docs.1 +++ b/deps/npm/man/man1/npm-docs.1 @@ -1,7 +1,8 @@ -.TH "NPM\-DOCS" "1" "October 2019" "" "" +.TH "NPM\-DOCS" "" "November 2019" "" "" .SH "NAME" -\fBnpm-docs\fR \- Docs for a package in a web browser maybe -.SH SYNOPSIS +\fBnpm-docs\fR +.SH Docs for a package in a web browser maybe +.SS Synopsis .P .RS 2 .nf @@ -11,14 +12,14 @@ npm home [<pkgname> [<pkgname> \.\.\.]] npm home \. .fi .RE -.SH DESCRIPTION +.SS Description .P This command tries to guess at the likely location of a package's documentation URL, and then tries to open it using the \fB\-\-browser\fP config param\. You can pass multiple package names at once\. If no package name is provided, it will search for a \fBpackage\.json\fP in the current folder and use the \fBname\fP property\. -.SH CONFIGURATION +.SS Configuration .SS browser .RS 0 .IP \(bu 2 @@ -39,22 +40,19 @@ Type: url .RE .P The base URL of the npm package registry\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help view +npm help npm\-view .IP \(bu 2 -npm help publish +npm help npm\-publish .IP \(bu 2 -npm help 7 registry +npm help registry .IP \(bu 2 -npm help config +npm help npm\-config .IP \(bu 2 -npm help 7 config +npm help npmrc .IP \(bu 2 -npm help 5 npmrc -.IP \(bu 2 -npm help 5 package\.json +npm help package\-json .RE - diff --git a/deps/npm/man/man1/npm-doctor.1 b/deps/npm/man/man1/npm-doctor.1 index 45a569b192..81c6aa1e90 100644 --- a/deps/npm/man/man1/npm-doctor.1 +++ b/deps/npm/man/man1/npm-doctor.1 @@ -1,14 +1,15 @@ -.TH "NPM\-DOCTOR" "1" "October 2019" "" "" +.TH "NPM\-DOCTOR" "" "November 2019" "" "" .SH "NAME" -\fBnpm-doctor\fR \- Check your environments -.SH SYNOPSIS +\fBnpm-doctor\fR +.SH Check your environments +.SS Synopsis .P .RS 2 .nf npm doctor .fi .RE -.SH DESCRIPTION +.SS Description .P \fBnpm doctor\fP runs a set of checks to ensure that your npm installation has what it needs to manage your JavaScript packages\. npm is mostly a standalone tool, but it does @@ -101,13 +102,13 @@ in your local cache (you can see where that cache is located with \fBnpm config get cache\fP, and see what's in that cache with \fBnpm cache ls\fP – probably more than you were expecting!)\. In the event that there are corrupt packages in your cache, you should probably run \fBnpm cache clean\fP and reset the cache\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help bugs +npm help npm\-bugs .IP \(bu 2 -npm help help +npm help npm\-help .IP \(bu 2 -npm help ping +npm help npm\-ping .RE diff --git a/deps/npm/man/man1/npm-edit.1 b/deps/npm/man/man1/npm-edit.1 index 01cf30c809..21e6d9ffad 100644 --- a/deps/npm/man/man1/npm-edit.1 +++ b/deps/npm/man/man1/npm-edit.1 @@ -1,19 +1,20 @@ -.TH "NPM\-EDIT" "1" "October 2019" "" "" +.TH "NPM\-EDIT" "" "November 2019" "" "" .SH "NAME" -\fBnpm-edit\fR \- Edit an installed package -.SH SYNOPSIS +\fBnpm-edit\fR +.SH Edit an installed package +.SS Synopsis .P .RS 2 .nf npm edit <pkg>[/<subpkg>\.\.\.] .fi .RE -.SH DESCRIPTION +.SS Description .P Selects a (sub)dependency in the current working directory and opens the package folder in the default editor (or whatever you've configured as the npm \fBeditor\fP config \-\- see -npm help 7 \fBnpm\-config\fP\|\.) +\fBnpm\-config\fP \fInpm\-config)\.\fR .P After it has been edited, the package is rebuilt so as to pick up any changes in compiled packages\. @@ -21,7 +22,7 @@ changes in compiled packages\. For instance, you can do \fBnpm install connect\fP to install connect into your package, and then \fBnpm edit connect\fP to make a few changes to your locally installed copy\. -.SH CONFIGURATION +.SS Configuration .SS editor .RS 0 .IP \(bu 2 @@ -33,20 +34,17 @@ Type: path .RE .P The command to run for \fBnpm edit\fP or \fBnpm config edit\fP\|\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help 5 folders +npm help folders .IP \(bu 2 -npm help explore +npm help npm\-explore .IP \(bu 2 -npm help install +npm help npm\-install .IP \(bu 2 -npm help config +npm help npm\-config .IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc +npm help npmrc .RE - diff --git a/deps/npm/man/man1/npm-explore.1 b/deps/npm/man/man1/npm-explore.1 index fed639636e..fa352a8ac4 100644 --- a/deps/npm/man/man1/npm-explore.1 +++ b/deps/npm/man/man1/npm-explore.1 @@ -1,14 +1,15 @@ -.TH "NPM\-EXPLORE" "1" "October 2019" "" "" +.TH "NPM\-EXPLORE" "" "November 2019" "" "" .SH "NAME" -\fBnpm-explore\fR \- Browse an installed package -.SH SYNOPSIS +\fBnpm-explore\fR +.SH description: Browse an installed package +.SS Synopsis .P .RS 2 .nf npm explore <pkg> [ \-\- <command>] .fi .RE -.SH DESCRIPTION +.SS Description .P Spawn a subshell in the directory of the installed package specified\. .P @@ -26,7 +27,7 @@ npm explore some\-dependency \-\- git pull origin master .P Note that the package is \fInot\fR automatically rebuilt afterwards, so be sure to use \fBnpm rebuild <pkg>\fP if you make any changes\. -.SH CONFIGURATION +.SS Configuration .SS shell .RS 0 .IP \(bu 2 @@ -38,18 +39,17 @@ Type: path .RE .P The shell to run for the \fBnpm explore\fP command\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help 5 folders +npm help folders .IP \(bu 2 -npm help edit +npm help npm\-edit .IP \(bu 2 -npm help rebuild +npm help npm\-rebuild .IP \(bu 2 -npm help build +npm help npm\-build .IP \(bu 2 -npm help install +npm help npm\-install .RE - diff --git a/deps/npm/man/man1/npm-fund.1 b/deps/npm/man/man1/npm-fund.1 new file mode 100644 index 0000000000..4468d31269 --- /dev/null +++ b/deps/npm/man/man1/npm-fund.1 @@ -0,0 +1,67 @@ +.TH "NPM\-FUND" "" "November 2019" "" "" +.SH "NAME" +\fBnpm-fund\fR +.SH Retrieve funding information +.SS Synopsis +.P +.RS 2 +.nf + npm fund [<pkg>] +.fi +.RE +.SS Description +.P +This command retrieves information on how to fund the dependencies of +a given project\. If no package name is provided, it will list all +dependencies that are looking for funding in a tree\-structure in which +are listed the type of funding and the url to visit\. If a package name +is provided then it tries to open its funding url using the \fB\-\-browser\fP +config param\. +.P +The list will avoid duplicated entries and will stack all packages +that share the same type/url as a single entry\. Given this nature the +list is not going to have the same shape of the output from \fBnpm ls\fP\|\. +.SS Configuration +.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 fund\fP command to open websites\. +.SS json +.RS 0 +.IP \(bu 2 +Default: false +.IP \(bu 2 +Type: Boolean + +.RE +.P +Show information in JSON format\. +.SS unicode +.RS 0 +.IP \(bu 2 +Type: Boolean +.IP \(bu 2 +Default: true + +.RE +.P +Whether to represent the tree structure using unicode characters\. +Set it to \fBfalse\fP in order to use all\-ansi output\. +.SH See Also +.RS 0 +.IP \(bu 2 +npm help npm\-docs +.IP \(bu 2 +npm help npm\-config +.IP \(bu 2 +npm help npm\-install +.IP \(bu 2 +npm help npm\-ls + +.RE diff --git a/deps/npm/man/man1/npm-help-search.1 b/deps/npm/man/man1/npm-help-search.1 index 2bbfc45051..bb29239dd2 100644 --- a/deps/npm/man/man1/npm-help-search.1 +++ b/deps/npm/man/man1/npm-help-search.1 @@ -1,14 +1,15 @@ -.TH "NPM\-HELP\-SEARCH" "1" "October 2019" "" "" +.TH "NPM\-HELP\-SEARCH" "" "November 2019" "" "" .SH "NAME" -\fBnpm-help-search\fR \- Search npm help documentation -.SH SYNOPSIS +\fBnpm-help-search\fR +.SH Search npm help documentation +.SS Synopsis .P .RS 2 .nf npm help\-search <text> .fi .RE -.SH DESCRIPTION +.SS Description .P This command will search the npm markdown documentation files for the terms provided, and then list the results, sorted by relevance\. @@ -18,7 +19,7 @@ If only one result is found, then it will show that help topic\. If the argument to \fBnpm help\fP is not a known help topic, then it will call \fBhelp\-search\fP\|\. It is rarely if ever necessary to call this command directly\. -.SH CONFIGURATION +.SS Configuration .SS long .RS 0 .IP \(bu 2 @@ -32,12 +33,11 @@ If true, the "long" flag will cause help\-search to output context around where the terms were found in the documentation\. .P If false, then help\-search will just list out the help topics found\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 npm help npm .IP \(bu 2 -npm help help +npm help npm\-help .RE - diff --git a/deps/npm/man/man1/npm-help.1 b/deps/npm/man/man1/npm-help.1 index c492a9c578..79849f7258 100644 --- a/deps/npm/man/man1/npm-help.1 +++ b/deps/npm/man/man1/npm-help.1 @@ -1,14 +1,15 @@ -.TH "NPM\-HELP" "1" "October 2019" "" "" +.TH "NPM\-HELP" "" "November 2019" "" "" .SH "NAME" -\fBnpm-help\fR \- Get help on npm -.SH SYNOPSIS +\fBnpm-help\fR +.SH Get help on npm +.SS Synopsis .P .RS 2 .nf npm help <term> [<terms\.\.>] .fi .RE -.SH DESCRIPTION +.SS Description .P If supplied a topic, then show the appropriate documentation page\. .P @@ -16,7 +17,7 @@ If the topic does not exist, or if multiple terms are provided, then run the \fBhelp\-search\fP command to find a match\. Note that, if \fBhelp\-search\fP finds a single subject, then it will run \fBhelp\fP on that topic, so unique matches are equivalent to specifying a topic name\. -.SH CONFIGURATION +.SS Configuration .SS viewer .RS 0 .IP \(bu 2 @@ -29,26 +30,19 @@ Type: path The program to use to view help content\. .P Set to \fB"browser"\fP to view html help content in the default web browser\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 npm help npm .IP \(bu 2 -README +npm help folders .IP \(bu 2 -npm help 5 folders +npm help npm\-config .IP \(bu 2 -npm help config +npm help npmrc .IP \(bu 2 -npm help 7 config +npm help package\-json .IP \(bu 2 -npm help 5 npmrc -.IP \(bu 2 -npm help 5 package\.json -.IP \(bu 2 -npm help help\-search -.IP \(bu 2 -npm help 7 index +npm help npm\-help\-search .RE - diff --git a/deps/npm/man/man1/npm-hook.1 b/deps/npm/man/man1/npm-hook.1 index a58d0f3264..9cab9c6e9c 100644 --- a/deps/npm/man/man1/npm-hook.1 +++ b/deps/npm/man/man1/npm-hook.1 @@ -1,7 +1,8 @@ -.TH "NPM\-HOOK" "1" "October 2019" "" "" +.TH "NPM\-HOOK" "" "November 2019" "" "" .SH "NAME" -\fBnpm-hook\fR \- Manage registry hooks -.SH SYNOPSIS +\fBnpm-hook\fR +.SH Manage registry hooks +.SS Synopsis .P .RS 2 .nf @@ -11,7 +12,7 @@ npm hook update <id> <url> [secret] npm hook rm <id> .fi .RE -.SH EXAMPLE +.SS Example .P Add a hook to watch a package for changes: .P @@ -68,7 +69,7 @@ Remove a hook: $ npm hook rm id\-deadbeef .fi .RE -.SH DESCRIPTION +.SS Description .P Allows you to manage npm hooks \fIhttps://blog\.npmjs\.org/post/145260155635/introducing\-hooks\-get\-notifications\-of\-npm\fR, @@ -89,7 +90,7 @@ that particular hook\. .P The shared secret will be sent along to the URL endpoint so you can verify the request came from your own configured hook\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 "Introducing Hooks" blog post \fIhttps://blog\.npmjs\.org/post/145260155635/introducing\-hooks\-get\-notifications\-of\-npm\fR diff --git a/deps/npm/man/man1/npm-init.1 b/deps/npm/man/man1/npm-init.1 index 60dfe54668..cfaa116a56 100644 --- a/deps/npm/man/man1/npm-init.1 +++ b/deps/npm/man/man1/npm-init.1 @@ -1,7 +1,8 @@ -.TH "NPM\-INIT" "1" "October 2019" "" "" +.TH "NPM\-INIT" "" "November 2019" "" "" .SH "NAME" -\fBnpm-init\fR \- create a package\.json file -.SH SYNOPSIS +\fBnpm-init\fR +.SH create a package\.json file +.SS Synopsis .P .RS 2 .nf @@ -10,7 +11,7 @@ npm init <@scope> (same as `npx <@scope>/create`) npm init [<@scope>/]<name> (same as `npx [<@scope>/]create\-<name>`) .fi .RE -.SH EXAMPLES +.SS Examples .P Create a new React\-based project using \fBcreate\-react\-app\fP \fIhttps://npm\.im/create\-react\-app\fR: .P @@ -46,12 +47,12 @@ Generate it without having it ask any questions: $ npm init \-y .fi .RE -.SH DESCRIPTION +.SS Description .P \fBnpm init <initializer>\fP can be used to set up a new or existing npm package\. .P \fBinitializer\fP in this case is an npm package named \fBcreate\-<initializer>\fP, which -will be installed by npm help \fBnpx\fP \fIhttps://npm\.im/npx\fR, and then have its main bin +will be installed by \fBnpx\fP \fIhttps://npm\.im/npx\fR, and then have its main bin executed \-\- presumably creating or updating \fBpackage\.json\fP and running any other initialization\-related operations\. .P @@ -76,16 +77,15 @@ existing fields, dependencies, and options selected\. It is strictly additive, s it will keep any fields and values that were already set\. You can also use \fB\-y\fP/\fB\-\-yes\fP to skip the questionnaire altogether\. If you pass \fB\-\-scope\fP, it will create a scoped package\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 https://github\.com/isaacs/init\-package\-json .IP \(bu 2 -npm help 5 package\.json +npm help package\-json .IP \(bu 2 -npm help version +npm help npm\-version .IP \(bu 2 -npm help 7 scope +npm help scope .RE - diff --git a/deps/npm/man/man1/npm-install-ci-test.1 b/deps/npm/man/man1/npm-install-ci-test.1 index 8c1c780d49..93cdb43bec 100644 --- a/deps/npm/man/man1/npm-install-ci-test.1 +++ b/deps/npm/man/man1/npm-install-ci-test.1 @@ -1,7 +1,8 @@ -.TH "NPM" "" "October 2019" "" "" +.TH "NPM" "" "November 2019" "" "" .SH "NAME" \fBnpm\fR -.SH SYNOPSIS +.SH Install a project with a clean slate and run tests +.SS Synopsis .P .RS 2 .nf @@ -10,14 +11,14 @@ npm install\-ci\-test alias: npm cit .fi .RE -.SH DESCRIPTION +.SS Description .P This command runs an \fBnpm ci\fP followed immediately by an \fBnpm test\fP\|\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help ci +npm help npm\-ci .IP \(bu 2 -npm help test +npm help npm\-test .RE diff --git a/deps/npm/man/man1/npm-install-test.1 b/deps/npm/man/man1/npm-install-test.1 index 6bf6aa325a..6df1508f1a 100644 --- a/deps/npm/man/man1/npm-install-test.1 +++ b/deps/npm/man/man1/npm-install-test.1 @@ -1,7 +1,8 @@ -.TH "NPM" "" "October 2019" "" "" +.TH "NPM" "" "November 2019" "" "" .SH "NAME" \fBnpm\fR -.SH SYNOPSIS +.SH Install package(s) and run tests +.SS Synopsis .P .RS 2 .nf @@ -18,16 +19,15 @@ alias: npm it common options: [\-\-save|\-\-save\-dev|\-\-save\-optional] [\-\-save\-exact] [\-\-dry\-run] .fi .RE -.SH DESCRIPTION +.SS Description .P This command runs an \fBnpm install\fP followed immediately by an \fBnpm test\fP\|\. It takes exactly the same arguments as \fBnpm install\fP\|\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help install +npm help npm\-install .IP \(bu 2 -npm help test +npm help npm\-test .RE - diff --git a/deps/npm/man/man1/npm-install.1 b/deps/npm/man/man1/npm-install.1 index 41d26b6217..564c306cad 100644 --- a/deps/npm/man/man1/npm-install.1 +++ b/deps/npm/man/man1/npm-install.1 @@ -1,7 +1,8 @@ -.TH "NPM\-INSTALL" "1" "October 2019" "" "" +.TH "NPM\-INSTALL" "" "November 2019" "" "" .SH "NAME" -\fBnpm-install\fR \- Install a package -.SH SYNOPSIS +\fBnpm-install\fR +.SH Install a package +.SS Synopsis .P .RS 2 .nf @@ -20,25 +21,25 @@ aliases: npm i, npm add common options: [\-P|\-\-save\-prod|\-D|\-\-save\-dev|\-O|\-\-save\-optional] [\-E|\-\-save\-exact] [\-B|\-\-save\-bundle] [\-\-no\-save] [\-\-dry\-run] .fi .RE -.SH DESCRIPTION +.SS Description .P This command installs a package, and any packages that it depends on\. If the package has a package\-lock or shrinkwrap file, the installation of dependencies will be driven by that, with an \fBnpm\-shrinkwrap\.json\fP taking precedence if both -files exist\. See npm help 5 package\-lock\.json and npm help shrinkwrap\. +files exist\. See package\-lock\.json \fI/docs/configuring\-npm/package\-lock\.json\fR and \fBnpm\-shrinkwrap\fP \fInpm\-shrinkwrap\fR\|\. .P A \fBpackage\fP is: .RS 0 .IP \(bu 2 -a) a folder containing a program described by a npm help 5 \fBpackage\.json\fP file +a) a folder containing a program described by a \fBpackage\.json\fP \fI/docs/configuring\-npm/package\-json\fR file .IP \(bu 2 b) a gzipped tarball containing (a) .IP \(bu 2 c) a url that resolves to (b) .IP \(bu 2 -d) a \fB<name>@<version>\fP that is published on the registry (see npm help 7 \fBnpm\-registry\fP) with (c) +d) a \fB<name>@<version>\fP that is published on the registry (see \fBnpm\-registry\fP \fInpm\-registry)\fR with (c) .IP \(bu 2 -e) a \fB<name>@<tag>\fP (see npm help \fBnpm\-dist\-tag\fP) that points to (d) +e) a \fB<name>@<tag>\fP (see \fBnpm\-dist\-tag\fP \fInpm\-dist\-tag)\fR that points to (d) .IP \(bu 2 f) a \fB<name>\fP that has a "latest" tag satisfying (e) .IP \(bu 2 @@ -58,7 +59,7 @@ after packing it up into a tarball (b)\. it installs the current package context (ie, the current working directory) as a global package\. By default, \fBnpm install\fP will install all modules listed as dependencies - in npm help 5 \fBpackage\.json\fP\|\. + in \fBpackage\.json\fP \fI/docs/configuring\-npm/package\-json\fR\|\. With the \fB\-\-production\fP flag (or when the \fBNODE_ENV\fP environment variable is set to \fBproduction\fP), npm will not install modules listed in \fBdevDependencies\fP\|\. @@ -110,7 +111,7 @@ npm install \./package\.tgz .IP \(bu 2 \fBnpm install [<@scope>/]<name>\fP: Do a \fB<name>@<tag>\fP install, where \fB<tag>\fP is the "tag" config\. (See - npm help 7 \fBnpm\-config\fP\|\. The config's default value is \fBlatest\fP\|\.) + \fBnpm\-config\fP \fI/docs/using\-npm/config\fR\|\. The config's default value is \fBlatest\fP\|\.) In most cases, this will install the version of the modules tagged as \fBlatest\fP on the npm registry\. Example: @@ -150,7 +151,7 @@ Further, if you have an \fBnpm\-shrinkwrap\.json\fP or \fBpackage\-lock\.json\fP will be updated as well\. \fB<scope>\fP is optional\. The package will be downloaded from the registry associated with the specified scope\. If no registry is associated with -the given scope the default registry is assumed\. See npm help 7 \fBnpm\-scope\fP\|\. +the given scope the default registry is assumed\. See \fBnpm\-scope\fP \fI/docs/using\-npm/scope\fR\|\. Note: if you do not include the @\-symbol on your scope name, npm will interpret this as a GitHub repository instead, see below\. Scopes names must also be followed by a slash\. @@ -167,19 +168,12 @@ npm install readable\-stream \-\-save\-exact npm install ansi\-regex \-\-save\-bundle .fi .RE - -.RE - -.RE -.P -.RS 2 -.nf -**Note**: If there is a file or folder named `<name>` in the current +.IP \(bu 2 +\fINote*\fR: If there is a file or folder named \fB<name>\fP in the current working directory, then it will try to install that, and only try to fetch the package by name if it is not valid\. -.fi + .RE -.RS 0 .IP \(bu 2 \fBnpm install [<@scope>/]<name>@<tag>\fP: Install the version of the package that is referenced by the specified tag\. @@ -189,8 +183,8 @@ fetch the package by name if it is not valid\. .P .RS 2 .nf - npm install sax@latest - npm install @myorg/mypackage@latest + npm install sax@latest + npm install @myorg/mypackage@latest .fi .RE .IP \(bu 2 @@ -201,22 +195,22 @@ fetch the package by name if it is not valid\. .P .RS 2 .nf - npm install sax@0\.1\.1 - npm install @myorg/privatepackage@1\.5\.0 + npm install sax@0\.1\.1 + npm install @myorg/privatepackage@1\.5\.0 .fi .RE .IP \(bu 2 \fBnpm install [<@scope>/]<name>@<version range>\fP: Install a version of the package matching the specified version range\. This - will follow the same rules for resolving dependencies described in npm help 5 \fBpackage\.json\fP\|\. + will follow the same rules for resolving dependencies described in \fBpackage\.json\fP \fI/docs/configuring\-npm/package\-json\fR\|\. Note that most version ranges must be put in quotes so that your shell will treat it as a single argument\. Example: .P .RS 2 .nf - npm install sax@">=0\.1\.0 <0\.2\.0" - npm install @myorg/privatepackage@">=0\.1\.0 <0\.2\.0" + npm install sax@">=0\.1\.0 <0\.2\.0" + npm install @myorg/privatepackage@">=0\.1\.0 <0\.2\.0" .fi .RE .IP \(bu 2 @@ -292,8 +286,8 @@ GIT_SSH_COMMAND='ssh \-i ~/\.ssh/custom_ident' npm install git+ssh://git@github\ .P .RS 2 .nf - npm install mygithubuser/myproject - npm install github:mygithubuser/myproject + npm install mygithubuser/myproject + npm install github:mygithubuser/myproject .fi .RE .IP \(bu 2 @@ -308,7 +302,7 @@ GIT_SSH_COMMAND='ssh \-i ~/\.ssh/custom_ident' npm install git+ssh://git@github\ .P .RS 2 .nf - npm install gist:101a11beef + npm install gist:101a11beef .fi .RE .IP \(bu 2 @@ -328,7 +322,7 @@ GIT_SSH_COMMAND='ssh \-i ~/\.ssh/custom_ident' npm install git+ssh://git@github\ .P .RS 2 .nf - npm install bitbucket:mybitbucketuser/myproject + npm install bitbucket:mybitbucketuser/myproject .fi .RE .IP \(bu 2 @@ -348,8 +342,8 @@ GIT_SSH_COMMAND='ssh \-i ~/\.ssh/custom_ident' npm install git+ssh://git@github\ .P .RS 2 .nf - npm install gitlab:mygitlabuser/myproject - npm install gitlab:myusr/myproj#semver:^5\.0 + npm install gitlab:mygitlabuser/myproject + npm install gitlab:myusr/myproj#semver:^5\.0 .fi .RE @@ -383,8 +377,12 @@ npm install sax \-\-force .fi .RE .P +The \fB\-\-no\-fund\fP argument will hide the message displayed at the end of each +install that aknowledges the number of dependencies looking for funding\. +See \fBnpm help fund\fP +.P The \fB\-g\fP or \fB\-\-global\fP argument will cause npm to install the package globally -rather than locally\. See npm help 5 \fBnpm\-folders\fP\|\. +rather than locally\. See npm\-folders \fI/docs/configuring\-npm/folders\fR\|\. .P The \fB\-\-global\-style\fP argument will cause npm to install the package into your local \fBnode_modules\fP folder with the same layout it uses with the @@ -393,7 +391,7 @@ global \fBnode_modules\fP folder\. Only your direct dependencies will show in \fBnode_modules\fP folders\. This obviously will eliminate some deduping\. .P The \fB\-\-ignore\-scripts\fP argument will cause npm to not execute any -scripts defined in the package\.json\. See npm help 7 \fBnpm\-scripts\fP\|\. +scripts defined in the package\.json\. See \fBnpm\-scripts\fP \fI/docs/using\-npm/scripts\fR\|\. .P The \fB\-\-legacy\-bundling\fP argument will cause npm to install the package such that versions of npm prior to 1\.4, such as the one included with node 0\.8, @@ -422,11 +420,11 @@ The \fB\-\-only={prod[uction]|dev[elopment]}\fP argument will cause either only \fBdevDependencies\fP or only non\-\fBdevDependencies\fP to be installed regardless of the \fBNODE_ENV\fP\|\. .P The \fB\-\-no\-audit\fP argument can be used to disable sending of audit reports to -the configured registries\. See npm help \fBnpm\-audit\fP for details on what is sent\. +the configured registries\. See \fBnpm\-audit\fP \fInpm\-audit\fR for details on what is sent\. .P -See npm help 7 \fBnpm\-config\fP\|\. Many of the configuration params have some +See \fBnpm\-config\fP \fI/docs/using\-npm/config\fR\|\. Many of the configuration params have some effect on installation, since that's most of what npm does\. -.SH ALGORITHM +.SS Algorithm .P To install a package, npm uses the following algorithm: .P @@ -478,7 +476,7 @@ privately for itself\. This algorithm is deterministic, but different trees may be produced if two dependencies are requested for installation in a different order\. .P -See npm help 5 folders for a more detailed description of the specific +See npm\-folders \fI/docs/configuring\-npm/folders\fR for a more detailed description of the specific folder structures that npm creates\. .SS Limitations of npm's Install Algorithm .P @@ -508,38 +506,37 @@ To avoid this situation, npm flat\-out refuses to install any folder ancestors\. A more correct, but more complex, solution would be to symlink the existing version into the new location\. If this ever affects a real use\-case, it will be investigated\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help 5 folders +npm help folders .IP \(bu 2 -npm help update +npm help npm\-update .IP \(bu 2 -npm help audit +npm help npm\-audit .IP \(bu 2 -npm help link +npm help npm\-fund .IP \(bu 2 -npm help rebuild +npm help npm\-link .IP \(bu 2 -npm help 7 scripts +npm help npm\-rebuild .IP \(bu 2 -npm help build +npm help scripts .IP \(bu 2 -npm help config +npm help npm\-build .IP \(bu 2 -npm help 7 config +npm help npm\-config .IP \(bu 2 -npm help 5 npmrc +npm help npmrc .IP \(bu 2 -npm help 7 registry +npm help registry .IP \(bu 2 -npm help dist\-tag +npm help npm\-dist\-tag .IP \(bu 2 -npm help uninstall +npm help npm\-uninstall .IP \(bu 2 -npm help shrinkwrap +npm help npm\-shrinkwrap .IP \(bu 2 -npm help 5 package\.json +npm help package\-json .RE - diff --git a/deps/npm/man/man1/npm-link.1 b/deps/npm/man/man1/npm-link.1 index 1d0d230914..b107c897d3 100644 --- a/deps/npm/man/man1/npm-link.1 +++ b/deps/npm/man/man1/npm-link.1 @@ -1,7 +1,8 @@ -.TH "NPM\-LINK" "1" "October 2019" "" "" +.TH "NPM\-LINK" "" "November 2019" "" "" .SH "NAME" -\fBnpm-link\fR \- Symlink a package folder -.SH SYNOPSIS +\fBnpm-link\fR +.SH Symlink a package folder +.SS Synopsis .P .RS 2 .nf @@ -11,13 +12,13 @@ npm link [<@scope>/]<pkg>[@<version>] alias: npm ln .fi .RE -.SH DESCRIPTION +.SS Description .P Package linking is a two\-step process\. .P First, \fBnpm link\fP in a package folder will create a symlink in the global folder \fB{prefix}/lib/node_modules/<package>\fP that links to the package where the \fBnpm -link\fP command was executed\. (see npm help 7 \fBnpm\-config\fP for the value of \fBprefix\fP)\. It +link\fP command was executed\. (see \fBnpm\-config\fP \fInpm\-config\fR for the value of \fBprefix\fP)\. It will also link any bins in the package to \fB{prefix}/bin/{name}\fP\|\. .P Next, in some other location, \fBnpm link package\-name\fP will create a @@ -27,7 +28,7 @@ of the current folder\. Note that \fBpackage\-name\fP is taken from \fBpackage\.json\fP, not from directory name\. .P -The package name can be optionally prefixed with a scope\. See npm help 7 \fBnpm\-scope\fP\|\. +The package name can be optionally prefixed with a scope\. See \fBnpm\-scope\fP \fInpm\-scope\fR\|\. The scope must be preceded by an @\-symbol and followed by a slash\. .P When creating tarballs for \fBnpm publish\fP, the linked packages are @@ -40,10 +41,10 @@ For example: .P .RS 2 .nf -cd ~/projects/node\-redis # go into the package directory -npm link # creates global link -cd ~/projects/node\-bloggy # go into some other package directory\. -npm link redis # link\-install the package + cd ~/projects/node\-redis # go into the package directory + npm link # creates global link + cd ~/projects/node\-bloggy # go into some other package directory\. + npm link redis # link\-install the package .fi .RE .P @@ -76,7 +77,7 @@ installation target into your project's \fBnode_modules\fP folder\. Note that in this case, you are referring to the directory name, \fBnode\-redis\fP, rather than the package name \fBredis\fP\|\. .P -If your linked package is scoped (see npm help 7 \fBnpm\-scope\fP) your link command must +If your linked package is scoped (see \fBnpm\-scope\fP \fInpm\-scope)\fR your link command must include that scope, e\.g\. .P .RS 2 @@ -84,22 +85,19 @@ include that scope, e\.g\. npm link @myorg/privatepackage .fi .RE -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help 7 developers +npm help developers .IP \(bu 2 -npm help 5 package\.json +npm help package\-json .IP \(bu 2 -npm help install +npm help npm\-install .IP \(bu 2 -npm help 5 folders +npm help folders .IP \(bu 2 -npm help config +npm help npm\-config .IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc +npm help npmrc .RE - diff --git a/deps/npm/man/man1/npm-logout.1 b/deps/npm/man/man1/npm-logout.1 index 5de250d38d..27e9b73293 100644 --- a/deps/npm/man/man1/npm-logout.1 +++ b/deps/npm/man/man1/npm-logout.1 @@ -1,14 +1,15 @@ -.TH "NPM\-LOGOUT" "1" "October 2019" "" "" +.TH "NPM\-LOGOUT" "" "November 2019" "" "" .SH "NAME" -\fBnpm-logout\fR \- Log out of the registry -.SH SYNOPSIS +\fBnpm-logout\fR +.SH Log out of the registry +.SS Synopsis .P .RS 2 .nf npm logout [\-\-registry=<url>] [\-\-scope=<@scope>] .fi .RE -.SH DESCRIPTION +.SS Description .P When logged into a registry that supports token\-based authentication, tell the server to end this token's session\. This will invalidate the token everywhere @@ -20,7 +21,7 @@ the current environment\. .P If \fB\-\-scope\fP is provided, this will find the credentials for the registry connected to that scope, if set\. -.SH CONFIGURATION +.SS Configuration .SS registry .P Default: https://registry\.npmjs\.org/ @@ -31,27 +32,22 @@ it takes precedence\. .P Default: The scope of your current project, if any, otherwise none\. .P -If specified, you will be logged out of the specified scope\. See npm help 7 \fBnpm\-scope\fP\|\. +If specified, you will be logged out of the specified scope\. See \fBnpm\-scope\fP \fInpm\-scope\fR\|\. .P .RS 2 .nf npm logout \-\-scope=@myco .fi .RE -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help adduser +npm help npm\-adduser .IP \(bu 2 -npm help 7 registry +npm help registry .IP \(bu 2 -npm help config +npm help npm\-config .IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc -.IP \(bu 2 -npm help whoami +npm help npm\-whoami .RE - diff --git a/deps/npm/man/man1/npm-ls.1 b/deps/npm/man/man1/npm-ls.1 index 9baeecc886..2574e9ede2 100644 --- a/deps/npm/man/man1/npm-ls.1 +++ b/deps/npm/man/man1/npm-ls.1 @@ -1,7 +1,8 @@ -.TH "NPM\-LS" "1" "October 2019" "" "" +.TH "NPM\-LS" "" "November 2019" "" "" .SH "NAME" -\fBnpm-ls\fR \- List installed packages -.SH SYNOPSIS +\fBnpm-ls\fR +.SH List installed packages +.SS Synopsis .P .RS 2 .nf @@ -10,7 +11,7 @@ npm ls [[<@scope>/]<pkg> \.\.\.] aliases: list, la, ll .fi .RE -.SH DESCRIPTION +.SS Description .P This command will print to stdout all the versions of packages that are installed, as well as their dependencies, in a tree\-structure\. @@ -22,9 +23,9 @@ For example, running \fBnpm ls promzard\fP in npm's source tree will show: .P .RS 2 .nf -npm@6.12.1 /path/to/npm -└─┬ init\-package\-json@0\.0\.4 - └── promzard@0\.1\.5 + npm@6\.13\.0 /path/to/npm + └─┬ init\-package\-json@0\.0\.4 + └── promzard@0\.1\.5 .fi .RE .P @@ -38,7 +39,7 @@ The tree shown is the logical dependency tree, based on package dependencies, not the physical layout of your node_modules folder\. .P When run as \fBll\fP or \fBla\fP, it shows extended information by default\. -.SH CONFIGURATION +.SS Configuration .SS json .RS 0 .IP \(bu 2 @@ -128,26 +129,34 @@ Default: false .RE .P Display only dependencies which are linked -.SH SEE ALSO +.SS unicode .RS 0 .IP \(bu 2 -npm help config +Type: Boolean .IP \(bu 2 -npm help 7 config +Default: true + +.RE +.P +Whether to represent the tree structure using unicode characters\. +Set it to false in order to use all\-ansi output\. +.SS See Also +.RS 0 +.IP \(bu 2 +npm help npm\-config .IP \(bu 2 -npm help 5 npmrc +npm help npmrc .IP \(bu 2 -npm help 5 folders +npm help folders .IP \(bu 2 -npm help install +npm help npm\-install .IP \(bu 2 -npm help link +npm help npm\-link .IP \(bu 2 -npm help prune +npm help npm\-prune .IP \(bu 2 -npm help outdated +npm help npm\-outdated .IP \(bu 2 -npm help update +npm help npm\-update .RE - diff --git a/deps/npm/man/man1/npm-org.1 b/deps/npm/man/man1/npm-org.1 index 2dc41214e3..67d3ebb47c 100644 --- a/deps/npm/man/man1/npm-org.1 +++ b/deps/npm/man/man1/npm-org.1 @@ -1,7 +1,8 @@ -.TH "NPM\-ORG" "1" "October 2019" "" "" +.TH "NPM\-ORG" "" "November 2019" "" "" .SH "NAME" -\fBnpm-org\fR \- Manage orgs -.SH SYNOPSIS +\fBnpm-org\fR +.SH Manage orgs +.SS Synopsis .P .RS 2 .nf @@ -10,7 +11,7 @@ npm org rm <orgname> <username> npm org ls <orgname> [<username>] .fi .RE -.SH EXAMPLE +.SS Example .P Add a new developer to an org: .P @@ -59,12 +60,12 @@ See what role a user has in an org: $ npm org ls my\-org @mx\-santos .fi .RE -.SH DESCRIPTION +.SS Description .P You can use the \fBnpm org\fP commands to manage and view users of an organization\. It supports adding and removing users, changing their roles, listing them, and finding specific ones and their roles\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 Documentation on npm Orgs \fIhttps://docs\.npmjs\.com/orgs/\fR diff --git a/deps/npm/man/man1/npm-outdated.1 b/deps/npm/man/man1/npm-outdated.1 index 7154ae46a7..93db219519 100644 --- a/deps/npm/man/man1/npm-outdated.1 +++ b/deps/npm/man/man1/npm-outdated.1 @@ -1,14 +1,15 @@ -.TH "NPM\-OUTDATED" "1" "October 2019" "" "" +.TH "NPM\-OUTDATED" "" "November 2019" "" "" .SH "NAME" -\fBnpm-outdated\fR \- Check for outdated packages -.SH SYNOPSIS +\fBnpm-outdated\fR +.SH Check for outdated packages +.SS Synopsis .P .RS 2 .nf npm outdated [[<@scope>/]<pkg> \.\.\.] .fi .RE -.SH DESCRIPTION +.SS Description .P This command will check the registry to see if any (or, specific) installed packages are currently outdated\. @@ -25,7 +26,7 @@ you're running \fBnpm outdated \-\-global\fP, or the package isn't included in Running \fBnpm publish\fP with no special configuration will publish the package with a dist\-tag of \fBlatest\fP\|\. This may or may not be the maximum version of the package, or the most\-recently published version of the package, depending -on how the package's developer manages the latest npm help dist\-tag\. +on how the package's developer manages the latest dist\-tag \fInpm\-dist\-tag\fR\|\. .IP \(bu 2 \fBlocation\fP is where in the dependency tree the package is located\. Note that \fBnpm outdated\fP defaults to a depth of 0, so unless you override that, you'll @@ -90,7 +91,7 @@ will install whatever's tagged as \fBlatest\fP\|\. running \fBnpm update\fP will bring it up to spec\. .RE -.SH CONFIGURATION +.SS Configuration .SS json .RS 0 .IP \(bu 2 @@ -142,16 +143,15 @@ Type: Int .RE .P Max depth for checking dependency tree\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help update +npm help npm\-update .IP \(bu 2 -npm help dist\-tag +npm help npm\-dist\-tag .IP \(bu 2 -npm help 7 registry +npm help registry .IP \(bu 2 -npm help 5 folders +npm help folders .RE - diff --git a/deps/npm/man/man1/npm-owner.1 b/deps/npm/man/man1/npm-owner.1 index 38b602d1d7..66a84f8be3 100644 --- a/deps/npm/man/man1/npm-owner.1 +++ b/deps/npm/man/man1/npm-owner.1 @@ -1,7 +1,8 @@ -.TH "NPM\-OWNER" "1" "October 2019" "" "" +.TH "NPM\-OWNER" "" "November 2019" "" "" .SH "NAME" -\fBnpm-owner\fR \- Manage package owners -.SH SYNOPSIS +\fBnpm-owner\fR +.SH Manage package owners +.SS Synopsis .P .RS 2 .nf @@ -12,7 +13,7 @@ npm owner ls [<@scope>/]<pkg> aliases: author .fi .RE -.SH DESCRIPTION +.SS Description .P Manage ownership of published packages\. .RS 0 @@ -38,16 +39,15 @@ that is not implemented at this time\. If you have two\-factor authentication enabled with \fBauth\-and\-writes\fP then you'll need to include an otp on the command line when changing ownership with \fB\-\-otp\fP\|\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help publish +npm help npm\-publish .IP \(bu 2 -npm help 7 registry +npm help registry .IP \(bu 2 -npm help adduser +npm help npm\-adduser .IP \(bu 2 -npm help 7 disputes +npm help disputes .RE - diff --git a/deps/npm/man/man1/npm-pack.1 b/deps/npm/man/man1/npm-pack.1 index fb7a8ce3b9..d035679478 100644 --- a/deps/npm/man/man1/npm-pack.1 +++ b/deps/npm/man/man1/npm-pack.1 @@ -1,14 +1,15 @@ -.TH "NPM\-PACK" "1" "October 2019" "" "" +.TH "NPM\-PACK" "" "November 2019" "" "" .SH "NAME" -\fBnpm-pack\fR \- Create a tarball from a package -.SH SYNOPSIS +\fBnpm-pack\fR +.SH Create a tarball from a package +.SS Synopsis .P .RS 2 .nf npm pack [[<@scope>/]<pkg>\.\.\.] [\-\-dry\-run] .fi .RE -.SH DESCRIPTION +.SS Description .P For anything that's installable (that is, a package folder, tarball, tarball url, name@tag, name@version, name, or scoped name), this @@ -23,18 +24,15 @@ If no arguments are supplied, then npm packs the current package folder\. .P The \fB\-\-dry\-run\fP argument will do everything that pack usually does without actually packing anything\. Reports on what would have gone into the tarball\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help cache +npm help npm\-cache .IP \(bu 2 -npm help publish +npm help npm\-publish .IP \(bu 2 -npm help config +npm help npm\-config .IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc +npm help npmrc .RE - diff --git a/deps/npm/man/man1/npm-ping.1 b/deps/npm/man/man1/npm-ping.1 index ac58e1f104..27df33858b 100644 --- a/deps/npm/man/man1/npm-ping.1 +++ b/deps/npm/man/man1/npm-ping.1 @@ -1,14 +1,15 @@ -.TH "NPM\-PING" "1" "October 2019" "" "" +.TH "NPM\-PING" "" "November 2019" "" "" .SH "NAME" -\fBnpm-ping\fR \- Ping npm registry -.SH SYNOPSIS +\fBnpm-ping\fR +.SH Ping npm registry +.SS Synopsis .P .RS 2 .nf npm ping [\-\-registry <registry>] .fi .RE -.SH DESCRIPTION +.SS Description .P Ping the configured or given npm registry and verify authentication\. If it works it will output something like: @@ -26,14 +27,11 @@ otherwise you will get: Ping error: {*Detail about error} .fi .RE -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help config +npm help npm\-config .IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc +npm help npmrc .RE - diff --git a/deps/npm/man/man1/npm-prefix.1 b/deps/npm/man/man1/npm-prefix.1 index d1f0bef968..d08fc57b73 100644 --- a/deps/npm/man/man1/npm-prefix.1 +++ b/deps/npm/man/man1/npm-prefix.1 @@ -1,35 +1,33 @@ -.TH "NPM\-PREFIX" "1" "October 2019" "" "" +.TH "NPM\-PREFIX" "" "November 2019" "" "" .SH "NAME" -\fBnpm-prefix\fR \- Display prefix -.SH SYNOPSIS +\fBnpm-prefix\fR +.SH Display prefix +.SS Synopsis .P .RS 2 .nf npm prefix [\-g] .fi .RE -.SH DESCRIPTION +.SS Description .P Print the local prefix to standard out\. This is the closest parent directory to contain a \fBpackage\.json\fP file or \fBnode_modules\fP directory, unless \fB\-g\fP is also specified\. .P If \fB\-g\fP is specified, this will be the value of the global prefix\. See -npm help 7 \fBnpm\-config\fP for more detail\. -.SH SEE ALSO +\fBnpm\-config\fP \fInpm\-config\fR for more detail\. +.SS See Also .RS 0 .IP \(bu 2 -npm help root +npm help npm\-root .IP \(bu 2 -npm help bin +npm help npm\-bin .IP \(bu 2 -npm help 5 folders +npm help folders .IP \(bu 2 -npm help config +npm help npm\-config .IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc +npm help npmrc .RE - diff --git a/deps/npm/man/man1/npm-profile.1 b/deps/npm/man/man1/npm-profile.1 index 7976f48c49..c19738ca7b 100644 --- a/deps/npm/man/man1/npm-profile.1 +++ b/deps/npm/man/man1/npm-profile.1 @@ -1,54 +1,6 @@ -.TH "NPM\-PROFILE" "1" "October 2019" "" "" -.SH "NAME" -\fBnpm-profile\fR \- Change settings on your registry profile -.SH SYNOPSIS .P -.RS 2 -.nf -npm profile get [\-\-json|\-\-parseable] [<property>] -npm profile set [\-\-json|\-\-parseable] <property> <value> -npm profile set password -npm profile enable\-2fa [auth\-and\-writes|auth\-only] -npm profile disable\-2fa -.fi -.RE -.SH DESCRIPTION -.P -Change your profile information on the registry\. This not be available if -you're using a non\-npmjs registry\. -.RS 0 -.IP \(bu 2 -\fBnpm profile get [<property>]\fP: -Display all of the properties of your profile, or one or more specific -properties\. It looks like: - -.RE -.P -.RS 2 -.nf -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| name | example | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| email | me@example\.com (verified) | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| two factor auth | auth\-and\-writes | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| fullname | Example User | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| homepage | | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| freenode | | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| twitter | | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| github | | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| created | 2015\-02\-26T01:38:35\.892Z | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| updated | 2017\-10\-02T21:29:45\.922Z | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -.fi -.RE ++ +``` .RS 0 .IP \(bu 2 \fBnpm profile set <property> <value>\fP: @@ -78,14 +30,14 @@ via \fBnpm access\fP and \fBnpm owner\fP\|\. Disables two\-factor authentication\. .RE -.SH DETAILS +.SS Details .P All of the \fBnpm profile\fP subcommands accept \fB\-\-json\fP and \fB\-\-parseable\fP and will tailor their output based on those\. Some of these commands may not be available on non npmjs\.com registries\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help 7 config +npm help npm\-config .RE diff --git a/deps/npm/man/man1/npm-prune.1 b/deps/npm/man/man1/npm-prune.1 index e34e5d13de..64a790fe7b 100644 --- a/deps/npm/man/man1/npm-prune.1 +++ b/deps/npm/man/man1/npm-prune.1 @@ -1,14 +1,15 @@ -.TH "NPM\-PRUNE" "1" "October 2019" "" "" +.TH "NPM\-PRUNE" "" "November 2019" "" "" .SH "NAME" -\fBnpm-prune\fR \- Remove extraneous packages -.SH SYNOPSIS +\fBnpm-prune\fR +.SH Remove extraneous packages +.SS Synopsis .P .RS 2 .nf npm prune [[<@scope>/]<pkg>\.\.\.] [\-\-production] [\-\-dry\-run] [\-\-json] .fi .RE -.SH DESCRIPTION +.SS Description .P This command removes "extraneous" packages\. If a package name is provided, then only packages matching one of the supplied names are @@ -33,14 +34,13 @@ this command with the \fB\-\-production\fP flag\. .P If you've disabled package\-locks then extraneous modules will not be removed and it's up to you to run \fBnpm prune\fP from time\-to\-time to remove them\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help uninstall +npm help npm\-uninstall .IP \(bu 2 -npm help 5 folders +npm help folders .IP \(bu 2 -npm help ls +npm help npm\-ls .RE - diff --git a/deps/npm/man/man1/npm-publish.1 b/deps/npm/man/man1/npm-publish.1 index a5bd2f901a..410be8799b 100644 --- a/deps/npm/man/man1/npm-publish.1 +++ b/deps/npm/man/man1/npm-publish.1 @@ -1,7 +1,8 @@ -.TH "NPM\-PUBLISH" "1" "October 2019" "" "" +.TH "NPM\-PUBLISH" "" "November 2019" "" "" .SH "NAME" -\fBnpm-publish\fR \- Publish a package -.SH SYNOPSIS +\fBnpm-publish\fR +.SH Publish a package +.SS Synopsis .P .RS 2 .nf @@ -11,18 +12,18 @@ Publishes '\.' if no argument supplied Sets tag 'latest' if no \-\-tag specified .fi .RE -.SH DESCRIPTION +.SS Description .P Publishes a package to the registry so that it can be installed by name\. All files in the package directory are included if no local \fB\|\.gitignore\fP or \fB\|\.npmignore\fP file exists\. If both files exist and a file is ignored by \fB\|\.gitignore\fP but not by \fB\|\.npmignore\fP then it will be included\. See -npm help 7 \fBnpm\-developers\fP for full details on what's included in the published +\fBnpm\-developers\fP \fI/docs/using\-npm/developers\fR for full details on what's included in the published package, as well as details on how the package is built\. .P By default npm will publish to the public registry\. This can be overridden by -specifying a different default registry or using a npm help 7 \fBnpm\-scope\fP in the name -(see npm help 5 \fBpackage\.json\fP)\. +specifying a different default registry or using a \fBnpm\-scope\fP \fInpm\-scope\fR in the name +(see \fBpackage\.json\fP \fI/docs/configuring\-npm/package\-json)\fR\|\. .RS 0 .IP \(bu 2 \fB<folder>\fP: @@ -35,7 +36,7 @@ with a package\.json file inside\. \fB[\-\-tag <tag>]\fP Registers the published package with the given tag, such that \fBnpm install <name>@<tag>\fP will install this version\. By default, \fBnpm publish\fP updates -and \fBnpm install\fP installs the \fBlatest\fP tag\. See npm help \fBnpm\-dist\-tag\fP for +and \fBnpm install\fP installs the \fBlatest\fP tag\. See \fBnpm\-dist\-tag\fP \fInpm\-dist\-tag\fR for details about tags\. .IP \(bu 2 \fB[\-\-access <public|restricted>]\fP @@ -60,32 +61,31 @@ the specified registry\. .P Once a package is published with a given name and version, that specific name and version combination can never be used again, even if -it is removed with npm help unpublish\. +it is removed with \fBnpm\-unpublish\fP \fInpm\-unpublish\fR\|\. .P As of \fBnpm@5\fP, both a sha1sum and an integrity field with a sha512sum of the tarball will be submitted to the registry during publication\. Subsequent installs will use the strongest supported algorithm to verify downloads\. .P -Similar to \fB\-\-dry\-run\fP see npm help \fBnpm\-pack\fP, which figures out the files to be +Similar to \fB\-\-dry\-run\fP see \fBnpm\-pack\fP \fInpm\-pack\fR, which figures out the files to be included and packs them into a tarball to be uploaded to the registry\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help 7 registry +npm help registry .IP \(bu 2 -npm help 7 scope +npm help scope .IP \(bu 2 -npm help adduser +npm help npm\-adduser .IP \(bu 2 -npm help owner +npm help npm\-owner .IP \(bu 2 -npm help deprecate +npm help npm\-deprecate .IP \(bu 2 -npm help dist\-tag +npm help npm\-dist\-tag .IP \(bu 2 -npm help pack +npm help npm\-pack .IP \(bu 2 -npm help profile +npm help npm\-profile .RE - diff --git a/deps/npm/man/man1/npm-rebuild.1 b/deps/npm/man/man1/npm-rebuild.1 index 2524e48ff7..e0b0975d17 100644 --- a/deps/npm/man/man1/npm-rebuild.1 +++ b/deps/npm/man/man1/npm-rebuild.1 @@ -1,7 +1,8 @@ -.TH "NPM\-REBUILD" "1" "October 2019" "" "" +.TH "NPM\-REBUILDD" "" "November 2019" "" "" .SH "NAME" -\fBnpm-rebuild\fR \- Rebuild a package -.SH SYNOPSIS +\fBnpm-rebuildd\fR +.SH Rebuild a package +.SS Synopsis .P .RS 2 .nf @@ -10,17 +11,16 @@ npm rebuild [[<@scope>/<name>]\.\.\.] alias: npm rb .fi .RE -.SH DESCRIPTION +.SS Description .P This command runs the \fBnpm build\fP command on the matched folders\. This is useful when you install a new version of node, and must recompile all your C++ addons with the new binary\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help build +npm help npm\-build .IP \(bu 2 -npm help install +npm help npm\-install .RE - diff --git a/deps/npm/man/man1/npm-repo.1 b/deps/npm/man/man1/npm-repo.1 index fe525f52db..c0e3e5e92b 100644 --- a/deps/npm/man/man1/npm-repo.1 +++ b/deps/npm/man/man1/npm-repo.1 @@ -1,20 +1,21 @@ -.TH "NPM\-REPO" "1" "October 2019" "" "" +.TH "NPM\-REPO" "" "November 2019" "" "" .SH "NAME" -\fBnpm-repo\fR \- Open package repository page in the browser -.SH SYNOPSIS +\fBnpm-repo\fR +.SH Open package repository page in the browser +.SS Synopsis .P .RS 2 .nf npm repo [<pkg>] .fi .RE -.SH DESCRIPTION +.SS Description .P This command tries to guess at the likely location of a package's repository URL, and then tries to open it using the \fB\-\-browser\fP config param\. If no package name is provided, it will search for a \fBpackage\.json\fP in the current folder and use the \fBname\fP property\. -.SH CONFIGURATION +.SS Configuration .SS browser .RS 0 .IP \(bu 2 @@ -25,12 +26,11 @@ Type: String .RE .P The browser that is called by the \fBnpm repo\fP command to open websites\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help docs +npm help npm\-docs .IP \(bu 2 -npm help config +npm help npm\-config .RE - diff --git a/deps/npm/man/man1/npm-restart.1 b/deps/npm/man/man1/npm-restart.1 index de134d0537..3c62324faf 100644 --- a/deps/npm/man/man1/npm-restart.1 +++ b/deps/npm/man/man1/npm-restart.1 @@ -1,14 +1,15 @@ -.TH "NPM\-RESTART" "1" "October 2019" "" "" +.TH "NPM\-RESTART" "" "November 2019" "" "" .SH "NAME" -\fBnpm-restart\fR \- Restart a package -.SH SYNOPSIS +\fBnpm-restart\fR +.SH Restart a package +.SS Synopsis .P .RS 2 .nf npm restart [\-\- <args>] .fi .RE -.SH DESCRIPTION +.SS Description .P This restarts a package\. .P @@ -35,27 +36,26 @@ poststart postrestart .RE -.SH NOTE +.SS Note .P Note that the "restart" script is run \fBin addition to\fR the "stop" and "start" scripts, not instead of them\. .P This is the behavior as of \fBnpm\fP major version 2\. A change in this behavior will be accompanied by an increase in major version number -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help run\-script +npm help npm\-run\-script .IP \(bu 2 -npm help 7 scripts +npm help /docs/using\-npm/scripts .IP \(bu 2 -npm help test +npm help npm\-test .IP \(bu 2 -npm help start +npm help npm\-start .IP \(bu 2 -npm help stop +npm help npm\-stop .IP \(bu 2 -npm apihelp restart +npm help npm\-restart .RE - diff --git a/deps/npm/man/man1/npm-root.1 b/deps/npm/man/man1/npm-root.1 index 665c8d4d31..a50ff39e3f 100644 --- a/deps/npm/man/man1/npm-root.1 +++ b/deps/npm/man/man1/npm-root.1 @@ -1,30 +1,28 @@ -.TH "NPM\-ROOT" "1" "October 2019" "" "" +.TH "NPM\-ROOT" "" "November 2019" "" "" .SH "NAME" -\fBnpm-root\fR \- Display npm root -.SH SYNOPSIS +\fBnpm-root\fR +.SH Display npm root +.SS Synopsis .P .RS 2 .nf npm root [\-g] .fi .RE -.SH DESCRIPTION +.SS Description .P Print the effective \fBnode_modules\fP folder to standard out\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help prefix +npm help npm\-prefix .IP \(bu 2 -npm help bin +npm help npm\-bin .IP \(bu 2 -npm help 5 folders +npm help folders .IP \(bu 2 -npm help config +npm help npm\-config .IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc +npm help npmrc .RE - diff --git a/deps/npm/man/man1/npm-run-script.1 b/deps/npm/man/man1/npm-run-script.1 index 18eb5fcc21..0896b9a8b3 100644 --- a/deps/npm/man/man1/npm-run-script.1 +++ b/deps/npm/man/man1/npm-run-script.1 @@ -1,7 +1,8 @@ -.TH "NPM\-RUN\-SCRIPT" "1" "October 2019" "" "" +.TH "NPM\-RUN\-SCRIPT" "" "November 2019" "" "" .SH "NAME" -\fBnpm-run-script\fR \- Run arbitrary package scripts -.SH SYNOPSIS +\fBnpm-run-script\fR +.SH Run arbitrary package scripts +.SS Synopsis .P .RS 2 .nf @@ -10,7 +11,7 @@ npm run\-script <command> [\-\-silent] [\-\- <args>\.\.\.] alias: npm run .fi .RE -.SH DESCRIPTION +.SS Description .P This runs an arbitrary command from a package's \fB"scripts"\fP object\. If no \fB"command"\fP is provided, it will list the available scripts\. \fBrun[\-script]\fP is @@ -86,20 +87,19 @@ You can use the \fB\-\-silent\fP flag to prevent showing \fBnpm ERR!\fP output o You can use the \fB\-\-if\-present\fP flag to avoid exiting with a non\-zero exit code when the script is undefined\. This lets you run potentially undefined scripts without breaking the execution chain\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help 7 scripts +npm help scripts .IP \(bu 2 -npm help test +npm help npm\-test .IP \(bu 2 -npm help start +npm help npm\-start .IP \(bu 2 -npm help restart +npm help npm\-restart .IP \(bu 2 -npm help stop +npm help npm\-stop .IP \(bu 2 -npm help 7 config +npm help npm\-config .RE - diff --git a/deps/npm/man/man1/npm-search.1 b/deps/npm/man/man1/npm-search.1 index a05e15d08e..037081c81a 100644 --- a/deps/npm/man/man1/npm-search.1 +++ b/deps/npm/man/man1/npm-search.1 @@ -1,7 +1,8 @@ -.TH "NPM\-SEARCH" "1" "October 2019" "" "" +.TH "NPM\-SEARCH" "" "November 2019" "" "" .SH "NAME" -\fBnpm-search\fR \- Search for packages -.SH SYNOPSIS +\fBnpm-search\fR +.SH Search for packages +.SS Synopsis .P .RS 2 .nf @@ -10,7 +11,7 @@ npm search [\-l|\-\-long] [\-\-json] [\-\-parseable] [\-\-no\-description] [sear aliases: s, se, find .fi .RE -.SH DESCRIPTION +.SS Description .P Search the registry for packages matching the search terms\. \fBnpm search\fP performs a linear, incremental, lexically\-ordered search through package @@ -32,7 +33,7 @@ supports standard JavaScript RegExp syntax\. A trailing \fB/\fP will be ignored this case\. (Note that many regular expression characters must be escaped or quoted in most shells\.) .SS A Note on caching -.SH CONFIGURATION +.SS Configuration .SS description .RS 0 .IP \(bu 2 @@ -121,18 +122,15 @@ to a different default registry, such as your internal private module repository, \fBnpm search\fP will default to that registry when searching\. Pass a different registry url such as the default above in order to override this setting\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help 7 registry +npm help registry .IP \(bu 2 -npm help config +npm help npm\-config .IP \(bu 2 -npm help 7 config +npm help npmrc .IP \(bu 2 -npm help 5 npmrc -.IP \(bu 2 -npm help view +npm help npm\-view .RE - diff --git a/deps/npm/man/man1/npm-shrinkwrap.1 b/deps/npm/man/man1/npm-shrinkwrap.1 index cdeea0c0dc..e5aa6917a9 100644 --- a/deps/npm/man/man1/npm-shrinkwrap.1 +++ b/deps/npm/man/man1/npm-shrinkwrap.1 @@ -1,38 +1,38 @@ -.TH "NPM\-SHRINKWRAP" "1" "October 2019" "" "" +.TH "NPM\-SHRINKWRAP" "" "November 2019" "" "" .SH "NAME" -\fBnpm-shrinkwrap\fR \- Lock down dependency versions for publication -.SH SYNOPSIS +\fBnpm-shrinkwrap\fR +.SH Lock down dependency versions for publication +.SS Synopsis .P .RS 2 .nf npm shrinkwrap .fi .RE -.SH DESCRIPTION +.SS Description .P This command repurposes \fBpackage\-lock\.json\fP into a publishable \fBnpm\-shrinkwrap\.json\fP or simply creates a new one\. The file created and updated by this command will then take precedence over any other existing or future \fBpackage\-lock\.json\fP files\. For a detailed explanation of the design and purpose -of package locks in npm, see npm help 5 package\-locks\. -.SH SEE ALSO +of package locks in npm, see npm\-package\-locks \fInpm\-package\-locks\fR\|\. +.SS See Also .RS 0 .IP \(bu 2 -npm help install +npm help npm\-install .IP \(bu 2 -npm help run\-script +npm help npm\-run\-script .IP \(bu 2 -npm help 7 scripts +npm help scripts .IP \(bu 2 -npm help 5 package\.json +npm help package\-json .IP \(bu 2 -npm help 5 package\-locks +npm help package\-locks .IP \(bu 2 -npm help 5 package\-lock\.json +npm help package\-lock\-json .IP \(bu 2 -npm help 5 shrinkwrap\.json +npm help shrinkwrap\-json .IP \(bu 2 -npm help ls +npm help npm\-ls .RE - diff --git a/deps/npm/man/man1/npm-star.1 b/deps/npm/man/man1/npm-star.1 index 04b338f36c..5aafda481f 100644 --- a/deps/npm/man/man1/npm-star.1 +++ b/deps/npm/man/man1/npm-star.1 @@ -1,7 +1,8 @@ -.TH "NPM\-STAR" "1" "October 2019" "" "" +.TH "NPM\-STAR" "" "November 2019" "" "" .SH "NAME" -\fBnpm-star\fR \- Mark your favorite packages -.SH SYNOPSIS +\fBnpm-star\fR +.SH Mark your favorite packages +.SS Synopsis .P .RS 2 .nf @@ -9,7 +10,7 @@ npm star [<pkg>\.\.\.] npm unstar [<pkg>\.\.\.] .fi .RE -.SH DESCRIPTION +.SS Description .P "Starring" a package means that you have some interest in it\. It's a vaguely positive way to show that you care\. @@ -17,14 +18,13 @@ a vaguely positive way to show that you care\. "Unstarring" is the same thing, but in reverse\. .P It's a boolean thing\. Starring repeatedly has no additional effect\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help view +npm help npm\-view .IP \(bu 2 -npm help whoami +npm help npm\-whoami .IP \(bu 2 -npm help adduser +npm help npm\-adduser .RE - diff --git a/deps/npm/man/man1/npm-stars.1 b/deps/npm/man/man1/npm-stars.1 index 0ea4b584c1..f68edfa96b 100644 --- a/deps/npm/man/man1/npm-stars.1 +++ b/deps/npm/man/man1/npm-stars.1 @@ -1,30 +1,30 @@ -.TH "NPM\-STARS" "1" "October 2019" "" "" +.TH "NPM\-STARS" "" "November 2019" "" "" .SH "NAME" -\fBnpm-stars\fR \- View packages marked as favorites -.SH SYNOPSIS +\fBnpm-stars\fR +.SH View packages marked as favorites +.SS Synopsis .P .RS 2 .nf npm stars [<user>] .fi .RE -.SH DESCRIPTION +.SS Description .P If you have starred a lot of neat things and want to find them again quickly this command lets you do just that\. .P You may also want to see your friend's favorite packages, in this case you will most certainly enjoy this command\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help star +npm help npm\-star .IP \(bu 2 -npm help view +npm help npm\-view .IP \(bu 2 -npm help whoami +npm help npm\-whoami .IP \(bu 2 -npm help adduser +npm help npm\-adduser .RE - diff --git a/deps/npm/man/man1/npm-start.1 b/deps/npm/man/man1/npm-start.1 index da7ea06320..72e59dedae 100644 --- a/deps/npm/man/man1/npm-start.1 +++ b/deps/npm/man/man1/npm-start.1 @@ -1,34 +1,34 @@ -.TH "NPM\-START" "1" "October 2019" "" "" +.TH "NPM\-START" "" "November 2019" "" "" .SH "NAME" -\fBnpm-start\fR \- Start a package -.SH SYNOPSIS +\fBnpm-start\fR +.SH Start a package +.SS Synopsis .P .RS 2 .nf npm start [\-\- <args>] .fi .RE -.SH DESCRIPTION +.SS Description .P This runs an arbitrary command specified in the package's \fB"start"\fP property of its \fB"scripts"\fP object\. If no \fB"start"\fP property is specified on the \fB"scripts"\fP object, it will run \fBnode server\.js\fP\|\. .P As of \fBnpm@2\.0\.0\fP \fIhttps://blog\.npmjs\.org/post/98131109725/npm\-2\-0\-0\fR, you can -use custom arguments when executing scripts\. Refer to npm help run\-script for +use custom arguments when executing scripts\. Refer to \fBnpm\-run\-script\fP \fInpm\-run\-script\fR for more details\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help run\-script +npm help npm\-run\-script .IP \(bu 2 -npm help 7 scripts +npm help scripts .IP \(bu 2 -npm help test +npm help npm\-test .IP \(bu 2 -npm help restart +npm help npm\-restart .IP \(bu 2 -npm help stop +npm help npm\-stop .RE - diff --git a/deps/npm/man/man1/npm-stop.1 b/deps/npm/man/man1/npm-stop.1 index e435b56f89..a2f6d92cfe 100644 --- a/deps/npm/man/man1/npm-stop.1 +++ b/deps/npm/man/man1/npm-stop.1 @@ -1,28 +1,28 @@ -.TH "NPM\-STOP" "1" "October 2019" "" "" +.TH "NPM\-STOP" "" "November 2019" "" "" .SH "NAME" -\fBnpm-stop\fR \- Stop a package -.SH SYNOPSIS +\fBnpm-stop\fR +.SH Stop a package +.SS Synopsis .P .RS 2 .nf npm stop [\-\- <args>] .fi .RE -.SH DESCRIPTION +.SS Description .P This runs a package's "stop" script, if one was provided\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help run\-script +npm help npm\-run\-script .IP \(bu 2 -npm help 7 scripts +npm help scripts .IP \(bu 2 -npm help test +npm help npm\-test .IP \(bu 2 -npm help start +npm help npm\-start .IP \(bu 2 -npm help restart +npm help npm\-restart .RE - diff --git a/deps/npm/man/man1/npm-team.1 b/deps/npm/man/man1/npm-team.1 index d4c2bf18e3..94fb186a19 100644 --- a/deps/npm/man/man1/npm-team.1 +++ b/deps/npm/man/man1/npm-team.1 @@ -1,7 +1,8 @@ -.TH "NPM\-TEAM" "1" "October 2019" "" "" +.TH "NPM\-TEAM" "" "November 2019" "" "" .SH "NAME" -\fBnpm-team\fR \- Manage organization teams and team memberships -.SH SYNOPSIS +\fBnpm-team\fR +.SH Manage organization teams and team memberships +.SS Synopsis .P .RS 2 .nf @@ -16,7 +17,7 @@ npm team ls <scope>|<scope:team> npm team edit <scope:team> .fi .RE -.SH DESCRIPTION +.SS Description .P Used to manage teams in organizations, and change team memberships\. Does not handle permissions for packages\. @@ -42,7 +43,7 @@ edit: Edit a current team\. .RE -.SH DETAILS +.SS Details .P \fBnpm team\fP always operates directly on the current registry, configurable from the command line using \fB\-\-registry=<registry url>\fP\|\. @@ -56,12 +57,11 @@ is done through the website, not the npm CLI\. .P To use teams to manage permissions on packages belonging to your organization, use the \fBnpm access\fP command to grant or revoke the appropriate permissions\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help access +npm help npm\-access .IP \(bu 2 -npm help 7 registry +npm help registry .RE - diff --git a/deps/npm/man/man1/npm-test.1 b/deps/npm/man/man1/npm-test.1 index b98fa1502a..c3d18a3eed 100644 --- a/deps/npm/man/man1/npm-test.1 +++ b/deps/npm/man/man1/npm-test.1 @@ -1,30 +1,30 @@ -.TH "NPM\-TEST" "1" "October 2019" "" "" +.TH "NPM\-TEST" "" "November 2019" "" "" .SH "NAME" -\fBnpm-test\fR \- Test a package -.SH SYNOPSIS +\fBnpm-test\fR +.SH Test a package +.SS Synopsis .P .RS 2 .nf - npm test [\-\- <args>] +npm test [\-\- <args>] - aliases: t, tst +aliases: t, tst .fi .RE -.SH DESCRIPTION +.SS Description .P This runs a package's "test" script, if one was provided\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help run\-script +npm help npm\-run\-script .IP \(bu 2 -npm help 7 scripts +npm help scripts .IP \(bu 2 -npm help start +npm help npm\-start .IP \(bu 2 -npm help restart +npm help npm\-restart .IP \(bu 2 -npm help stop +npm help npm\-stop .RE - diff --git a/deps/npm/man/man1/npm-token.1 b/deps/npm/man/man1/npm-token.1 index f71a5c03ba..f52451cae0 100644 --- a/deps/npm/man/man1/npm-token.1 +++ b/deps/npm/man/man1/npm-token.1 @@ -1,78 +1,6 @@ -.TH "NPM\-TOKEN" "1" "October 2019" "" "" -.SH "NAME" -\fBnpm-token\fR \- Manage your authentication tokens -.SH SYNOPSIS .P -.RS 2 -.nf -npm token list [\-\-json|\-\-parseable] -npm token create [\-\-read\-only] [\-\-cidr=1\.1\.1\.1/24,2\.2\.2\.2/16] -npm token revoke <id|token> -.fi -.RE -.SH DESCRIPTION -.P -This lets you list, create and revoke authentication tokens\. -.RS 0 -.IP \(bu 2 -\fBnpm token list\fP: -Shows a table of all active authentication tokens\. You can request this as -JSON with \fB\-\-json\fP or tab\-separated values with \fB\-\-parseable\fP\|\. ++ ``` -.IP \(bu 2 -\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| id | token | created | read\-only | CIDR whitelist | -.IP \(bu 2 -\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| 7f3134 | 1fa9ba… | 2017\-10\-02 | yes | | -.IP \(bu 2 -\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| c03241 | af7aef… | 2017\-10\-02 | no | 192\.168\.0\.1/24 | -.IP \(bu 2 -\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| e0cf92 | 3a436a… | 2017\-10\-02 | no | | -.IP \(bu 2 -\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| 63eb9d | 74ef35… | 2017\-09\-28 | no | | -.IP \(bu 2 -\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| 2daaa8 | cbad5f… | 2017\-09\-26 | no | | -.IP \(bu 2 -\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| 68c2fe | 127e51… | 2017\-09\-23 | no | | -.IP \(bu 2 -\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| 6334e1 | 1dadd1… | 2017\-09\-23 | no | | -.IP \(bu 2 -\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -.P -.RS 2 -.nf - -.fi -.RE -.IP \(bu 2 -\fBnpm token create [\-\-read\-only] [\-\-cidr=<cidr\-ranges>]\fP: -Create a new authentication token\. It can be \fB\-\-read\-only\fP or accept a list of -CIDR \fIhttps://en\.wikipedia\.org/wiki/Classless_Inter\-Domain_Routing\fR ranges to -limit use of this token to\. This will prompt you for your password, and, if you have -two\-factor authentication enabled, an otp\. - -.RE -.P -.RS 2 -.nf -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| token | a73c9572\-f1b9\-8983\-983d\-ba3ac3cc913d | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| cidr_whitelist | | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| readonly | false | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| created | 2017\-10\-02T07:52:24\.838Z | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -.fi -.RE .RS 0 .IP \(bu 2 \fBnpm token revoke <token|id>\fP: diff --git a/deps/npm/man/man1/npm-uninstall.1 b/deps/npm/man/man1/npm-uninstall.1 index f1be6e3cf9..4be083e6f8 100644 --- a/deps/npm/man/man1/npm-uninstall.1 +++ b/deps/npm/man/man1/npm-uninstall.1 @@ -1,7 +1,8 @@ -.TH "NPM\-UNINSTALL" "1" "October 2019" "" "" +.TH "NPM\-UNINSTALL" "" "November 2019" "" "" .SH "NAME" -\fBnpm-uninstall\fR \- Remove a package -.SH SYNOPSIS +\fBnpm-uninstall\fR +.SH Remove a package +.SS Synopsis .P .RS 2 .nf @@ -10,7 +11,7 @@ npm uninstall [<@scope>/]<pkg>[@<version>]\.\.\. [\-S|\-\-save|\-D|\-\-save\-dev aliases: remove, rm, r, un, unlink .fi .RE -.SH DESCRIPTION +.SS Description .P This uninstalls a package, completely removing everything npm installed on its behalf\. @@ -43,7 +44,7 @@ the package version in your main package\.json: Further, if you have an \fBnpm\-shrinkwrap\.json\fP then it will be updated as well\. .P -Scope is optional and follows the usual rules for npm help 7 \fBnpm\-scope\fP\|\. +Scope is optional and follows the usual rules for \fBnpm\-scope\fP \fIsnpm\-scope\fR\|\. .P Examples: .P @@ -56,20 +57,17 @@ npm uninstall dtrace\-provider \-\-save\-optional npm uninstall lodash \-\-no\-save .fi .RE -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help prune +npm help npm\-prune .IP \(bu 2 -npm help install +npm help npm\-install .IP \(bu 2 -npm help 5 folders +npm help folders .IP \(bu 2 -npm help config +npm help npm\-config .IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc +npm help npmrc .RE - diff --git a/deps/npm/man/man1/npm-unpublish.1 b/deps/npm/man/man1/npm-unpublish.1 index 620f02c885..5e2f8dac49 100644 --- a/deps/npm/man/man1/npm-unpublish.1 +++ b/deps/npm/man/man1/npm-unpublish.1 @@ -1,14 +1,15 @@ -.TH "NPM\-UNPUBLISH" "1" "October 2019" "" "" +.TH "NPM\-UNPUBLISH" "" "November 2019" "" "" .SH "NAME" -\fBnpm-unpublish\fR \- Remove a package from the registry -.SH SYNOPSIS +\fBnpm-unpublish\fR +.SH Remove a package from the registry +.SS Synopsis .P .RS 2 .nf npm unpublish [<@scope>/]<pkg>[@<version>] .fi .RE -.SH WARNING +.SS Warning .P \fBIt is generally considered bad behavior to remove versions of a library that others are depending on!\fR @@ -17,7 +18,7 @@ Consider using the \fBdeprecate\fP command instead, if your intent is to encourage users to upgrade\. .P There is plenty of room on the registry\. -.SH DESCRIPTION +.SS Description .P This removes a package version from the registry, deleting its entry and removing the tarball\. @@ -36,19 +37,18 @@ only allowed with versions published in the last 72 hours\. If you are trying to unpublish a version published longer ago than that, contact support@npmjs\.com\|\. .P -The scope is optional and follows the usual rules for npm help 7 \fBnpm\-scope\fP\|\. -.SH SEE ALSO +The scope is optional and follows the usual rules for \fBnpm\-scope\fP \fI/docs/using\-npm/scope\fR\|\. +.SS See Also .RS 0 .IP \(bu 2 -npm help deprecate +npm help npm\-deprecate .IP \(bu 2 -npm help publish +npm help npm\-publish .IP \(bu 2 -npm help 7 registry +npm help registry .IP \(bu 2 -npm help adduser +npm help npm\-adduser .IP \(bu 2 -npm help owner +npm help npm\-owner .RE - diff --git a/deps/npm/man/man1/npm-update.1 b/deps/npm/man/man1/npm-update.1 index 0bc252aff0..3b78a687e2 100644 --- a/deps/npm/man/man1/npm-update.1 +++ b/deps/npm/man/man1/npm-update.1 @@ -1,7 +1,8 @@ -.TH "NPM\-UPDATE" "1" "October 2019" "" "" +.TH "NPM\-UPDATE" "" "November 2019" "" "" .SH "NAME" -\fBnpm-update\fR \- Update a package -.SH SYNOPSIS +\fBnpm-update\fR +.SH Update a package +.SS Synopsis .P .RS 2 .nf @@ -10,7 +11,7 @@ npm update [\-g] [<pkg>\.\.\.] aliases: up, upgrade .fi .RE -.SH DESCRIPTION +.SS Description .P This command will update all the packages listed to the latest version (specified by the \fBtag\fP config), respecting semver\. @@ -32,7 +33,7 @@ To get the old behavior, use \fBnpm \-\-depth 9999 update\fP\|\. As of \fBnpm@5\.0\.0\fP, the \fBnpm update\fP will change \fBpackage\.json\fP to save the new version as the minimum required dependency\. To get the old behavior, use \fBnpm update \-\-no\-save\fP\|\. -.SH EXAMPLES +.SS Example .P IMPORTANT VERSION NOTE: these examples assume \fBnpm@2\.6\.1\fP or later\. For older versions of \fBnpm\fP, you must specify \fB\-\-depth 0\fP to get the behavior @@ -124,20 +125,19 @@ package that is \fBoutdated\fP \-\- that is, has a version that is different fro .P NOTE: If a package has been upgraded to a version newer than \fBlatest\fP, it will be \fIdowngraded\fR\|\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help install +npm help npm\-install .IP \(bu 2 -npm help outdated +npm help npm\-outdated .IP \(bu 2 -npm help shrinkwrap +npm help npm\-shrinkwrap .IP \(bu 2 -npm help 7 registry +npm help registry .IP \(bu 2 -npm help 5 folders +npm help folders .IP \(bu 2 -npm help ls +npm help npm\-ls .RE - diff --git a/deps/npm/man/man1/npm-version.1 b/deps/npm/man/man1/npm-version.1 index 3be068b773..42f6bee330 100644 --- a/deps/npm/man/man1/npm-version.1 +++ b/deps/npm/man/man1/npm-version.1 @@ -1,7 +1,8 @@ -.TH "NPM\-VERSION" "1" "October 2019" "" "" +.TH "NPM\-VERSION" "" "November 2019" "" "" .SH "NAME" -\fBnpm-version\fR \- Bump a package version -.SH SYNOPSIS +\fBnpm-version\fR +.SH Bump a package version +.SS Synopsis .P .RS 2 .nf @@ -12,7 +13,7 @@ npm version [<newversion> | major | minor | patch | premajor | preminor | prepat \|'npm ls' to inspect current package/dependency versions .fi .RE -.SH DESCRIPTION +.SS Description .P Run this in a package directory to bump the version and write the new data back to \fBpackage\.json\fP, \fBpackage\-lock\.json\fP, and, if present, \fBnpm\-shrinkwrap\.json\fP\|\. @@ -88,18 +89,18 @@ Take the following example: .P .RS 2 .nf -"scripts": { - "preversion": "npm test", - "version": "npm run build && git add \-A dist", - "postversion": "git push && git push \-\-tags && rm \-rf build/temp" -} + "scripts": { + "preversion": "npm test", + "version": "npm run build && git add \-A dist", + "postversion": "git push && git push \-\-tags && rm \-rf build/temp" + } .fi .RE .P This runs all your tests, and proceeds only if they pass\. Then runs your \fBbuild\fP script, and adds everything in the \fBdist\fP directory to the commit\. After the commit, it pushes the new commit and tag up to the server, and deletes the \fBbuild/temp\fP directory\. -.SH CONFIGURATION +.SS Configuration .SS allow\-same\-version .RS 0 .IP \(bu 2 @@ -143,20 +144,19 @@ Type: Boolean Pass the \fB\-s\fP flag to git to sign the tag\. .P Note that you must have a default GPG key set up in your git config for this to work properly\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help init +npm help npm\-init .IP \(bu 2 -npm help run\-script +npm help npm\-run\-script .IP \(bu 2 -npm help 7 scripts +npm help scripts .IP \(bu 2 -npm help 5 package\.json +package\.json \fI/docs/configuring\-npm/package\-json\fR .IP \(bu 2 -npm help 7 semver +npm help semver .IP \(bu 2 -npm help 7 config +npm help config .RE - diff --git a/deps/npm/man/man1/npm-view.1 b/deps/npm/man/man1/npm-view.1 index b4dacc8d9b..156fd1eae0 100644 --- a/deps/npm/man/man1/npm-view.1 +++ b/deps/npm/man/man1/npm-view.1 @@ -1,7 +1,8 @@ -.TH "NPM\-VIEW" "1" "October 2019" "" "" +.TH "NPM\-VIEW" "" "November 2019" "" "" .SH "NAME" -\fBnpm-view\fR \- View registry info -.SH SYNOPSIS +\fBnpm-view\fR +.SH View registry info +.SS Synopsis .P .RS 2 .nf @@ -10,7 +11,7 @@ npm view [<@scope>/]<name>[@<version>] [<field>[\.<subfield>]\.\.\.] aliases: info, show, v .fi .RE -.SH DESCRIPTION +.SS Description .P This command shows data about a package and prints it to the stream referenced by the \fBoutfd\fP config, which defaults to stdout\. @@ -88,7 +89,7 @@ npm view express contributors\.name contributors\.email .P "Person" fields are shown as a string if they would be shown as an object\. So, for example, this will show the list of npm contributors in -the shortened string format\. (See npm help 5 \fBpackage\.json\fP for more on this\.) +the shortened string format\. (See \fBpackage\.json\fP \fI/docs/configuring\-npm/package\.json\fR for more on this\.) .P .RS 2 .nf @@ -114,7 +115,7 @@ this: npm view connect versions .fi .RE -.SH OUTPUT +.SS Output .P If only a single string field for a single version is output, then it will not be colorized or quoted, so as to enable piping the output to @@ -127,20 +128,17 @@ will be prefixed with the version it applies to\. .P If multiple fields are requested, than each of them are prefixed with the field name\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help search +npm help npm\-search .IP \(bu 2 -npm help 7 registry +npm help registry .IP \(bu 2 -npm help config +npm help npm\-config .IP \(bu 2 -npm help 7 config +npm help npmrc .IP \(bu 2 -npm help 5 npmrc -.IP \(bu 2 -npm help docs +npm help npm\-docs .RE - diff --git a/deps/npm/man/man1/npm-whoami.1 b/deps/npm/man/man1/npm-whoami.1 index d6811a0e8f..ea09d40c02 100644 --- a/deps/npm/man/man1/npm-whoami.1 +++ b/deps/npm/man/man1/npm-whoami.1 @@ -1,26 +1,24 @@ -.TH "NPM\-WHOAMI" "1" "October 2019" "" "" +.TH "NPM\-WHOAMI" "" "November 2019" "" "" .SH "NAME" -\fBnpm-whoami\fR \- Display npm username -.SH SYNOPSIS +\fBnpm-whoami\fR +.SH Display npm username +.SS Synopsis .P .RS 2 .nf npm whoami [\-\-registry <registry>] .fi .RE -.SH DESCRIPTION +.SS Description .P Print the \fBusername\fP config to standard output\. -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help config +npm help npm\-config .IP \(bu 2 -npm help 7 config +npm help npmrc .IP \(bu 2 -npm help 5 npmrc -.IP \(bu 2 -npm help adduser +npm help npm\-adduser .RE - diff --git a/deps/npm/man/man1/npm.1 b/deps/npm/man/man1/npm.1 index 8d198b4a2d..525990c758 100644 --- a/deps/npm/man/man1/npm.1 +++ b/deps/npm/man/man1/npm.1 @@ -1,17 +1,18 @@ -.TH "NPM" "1" "October 2019" "" "" +.TH "NPM" "" "November 2019" "" "" .SH "NAME" -\fBnpm\fR \- javascript package manager -.SH SYNOPSIS +\fBnpm\fR +.SH javascript package manager +.SS Synopsis .P .RS 2 .nf npm <command> [args] .fi .RE -.SH VERSION +.SS Version .P -6.12.1 -.SH DESCRIPTION +6\.13\.0 +.SS Description .P npm is the package manager for the Node JavaScript platform\. It puts modules in place so that node can find them, and manages dependency @@ -22,7 +23,7 @@ Most commonly, it is used to publish, discover, install, and develop node programs\. .P Run \fBnpm help\fP to get a list of available commands\. -.SH IMPORTANT +.SS Important .P npm is configured to use npm, Inc\.'s public registry at https://registry\.npmjs\.org by default\. Use of the npm public registry is @@ -31,16 +32,16 @@ subject to terms of use available at https://www\.npmjs\.com/policies/terms\. You can configure npm to use any compatible registry you like, and even run your own registry\. Use of someone else's registry may be governed by their terms of use\. -.SH INTRODUCTION +.SS Introduction .P You probably got npm because you want to install stuff\. .P Use \fBnpm install blerg\fP to install the latest version of "blerg"\. Check out -npm help \fBnpm\-install\fP for more info\. It can do a lot of stuff\. +\fBnpm\-install\fP \fInpm\-install\fR for more info\. It can do a lot of stuff\. .P Use the \fBnpm search\fP command to show everything that's available\. Use \fBnpm ls\fP to show everything you've installed\. -.SH DEPENDENCIES +.SS Dependencies .P If a package references to another package with a git URL, npm depends on a preinstalled git\. @@ -55,9 +56,9 @@ not supported by node\-gyp \fIhttps://github\.com/TooTallNate/node\-gyp\fR\|\. For more information visit the node\-gyp repository \fIhttps://github\.com/TooTallNate/node\-gyp\fR and the node\-gyp Wiki \fIhttps://github\.com/TooTallNate/node\-gyp/wiki\fR\|\. -.SH DIRECTORIES +.SS Directories .P -See npm help 5 \fBnpm\-folders\fP to learn about where npm puts stuff\. +See \fBnpm\-folders\fP \fI/docs/configuring\-npm/folders\fR to learn about where npm puts stuff\. .P In particular, npm has two modes of operation: .RS 0 @@ -75,14 +76,14 @@ defaults to the current working directory\. Packages are installed to .P Local mode is the default\. Use \fB\-g\fP or \fB\-\-global\fP on any command to operate in global mode instead\. -.SH DEVELOPER USAGE +.SS Developer Usage .P If you're using npm to develop and publish your code, check out the following help topics: .RS 0 .IP \(bu 2 json: -Make a package\.json file\. See npm help 5 \fBpackage\.json\fP\|\. +Make a package\.json file\. See \fBpackage\.json\fP \fI/docs/configuring\-npm/package\.json\fR\|\. .IP \(bu 2 link: For linking your current working code into Node's path, so that you @@ -102,7 +103,7 @@ publish: Use the \fBnpm publish\fP command to upload your code to the registry\. .RE -.SH CONFIGURATION +.SS Configuration .P npm is extremely configurable\. It reads its configuration options from 5 places\. @@ -135,8 +136,8 @@ lib/utils/config\-defs\.js\. These must not be changed\. .RE .P -See npm help 7 \fBnpm\-config\fP for much much more information\. -.SH CONTRIBUTIONS +See \fBnpm\-config\fP \fI/docs/using\-npm/config\fR for much much more information\. +.SS Contributions .P Patches welcome! .P @@ -151,7 +152,7 @@ Bug tracker \fIhttps://npm\.community/c/bugs\fR Support tracker \fIhttps://npm\.community/c/support\fR .RE -.SH BUGS +.SS Bugs .P When you find issues, please report them: .RS 0 @@ -165,30 +166,23 @@ Be sure to follow the template and bug reporting guidelines\. You can also ask for help in the support forum \fIhttps://npm\.community/c/support\fR if you're unsure if it's actually a bug or are having trouble coming up with a detailed reproduction to report\. -.SH AUTHOR +.SS Author .P Isaac Z\. Schlueter \fIhttp://blog\.izs\.me/\fR :: isaacs \fIhttps://github\.com/isaacs/\fR :: @izs \fIhttps://twitter\.com/izs\fR :: i@izs\.me -.SH SEE ALSO +.SS See Also .RS 0 .IP \(bu 2 -npm help help +npm help npm\-help .IP \(bu 2 -README +npm help package\-json .IP \(bu 2 -npm help 5 package\.json +npm help npm\-install .IP \(bu 2 -npm help install +npm help npm\-config .IP \(bu 2 -npm help config -.IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc -.IP \(bu 2 -npm help 7 index +npm help npmrc .RE - |