deps: upgrade npm to 6.13.1

PR-URL: https://github.com/nodejs/node/pull/30533 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Jiawen Geng <technicalcute@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
author: claudiahdz <cghr1990@gmail.com> 2019-11-18 21:01:39 +0200
committer: Myles Borins <mylesborins@google.com> 2019-11-20 19:16:47 -0500
commit: a7c7c703aff362f06ef5d49451a0f79fd289910f (patch)
tree: 48f9d01b32d55d420f229c4889a5a61178419223 /deps/npm/man
parent: a30a9f8193ddd61dfadc2d5d79784b682027b319 (diff)
download: node-new-a7c7c703aff362f06ef5d49451a0f79fd289910f.tar.gz
78 files changed, 510 insertions, 791 deletions
diff --git a/deps/npm/man/man1/npm-README.1 b/deps/npm/man/man1/npm-README.1
index 73e841ba88..c2535cc28a 100644
--- a/deps/npm/man/man1/npm-README.1
+++ b/deps/npm/man/man1/npm-README.1
@@ -1,6 +1,6 @@
-.TH "NPM" "" "November 2019" "" ""
+.TH "NPM" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm\fR
+\fBnpm\fR \- a JavaScript package manager
 .P
 Build Status \fIhttps://img\.shields\.io/travis/npm/cli/latest\.svg\fR \fIhttps://travis\-ci\.org/npm/cli\fR
 .SH SYNOPSIS
@@ -165,8 +165,8 @@ doubt tell you to put the output in a gist or email\.
 .SH SEE ALSO
 .RS 0
 .IP \(bu 2
-npm help npm
+npm(1)
 .IP \(bu 2
-npm help help
+npm\-help(1)
 
 .RE
diff --git a/deps/npm/man/man1/npm-access.1 b/deps/npm/man/man1/npm-access.1
index 8bd724d066..ac6274bacd 100644
--- a/deps/npm/man/man1/npm-access.1
+++ b/deps/npm/man/man1/npm-access.1
@@ -1,7 +1,6 @@
-.TH "NPM\-ACCESS" "" "November 2019" "" ""
+.TH "NPM\-ACCESS" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-access\fR
-.SH Set access level on published packages
+\fBnpm-access\fR \- Set access level on published packages
 .SS Synopsis
 .P
 .RS 2
@@ -90,11 +89,11 @@ Management of teams and team memberships is done with the \fBnpm team\fP command
 .IP \(bu 2
 \fBlibnpmaccess\fP \fIhttps://npm\.im/libnpmaccess\fR
 .IP \(bu 2
-npm help npm\-team
+npm help team
 .IP \(bu 2
-npm help npm\-publish
+npm help publish
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
 npm help registry
 
diff --git a/deps/npm/man/man1/npm-adduser.1 b/deps/npm/man/man1/npm-adduser.1
index f8c75cc715..89cda80297 100644
--- a/deps/npm/man/man1/npm-adduser.1
+++ b/deps/npm/man/man1/npm-adduser.1
@@ -1,7 +1,6 @@
-.TH "NPM\-ADDUSER" "" "November 2019" "" ""
+.TH "NPM\-ADDUSER" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-adduser\fR
-.SH Add a registry user account
+\fBnpm-adduser\fR \- Add a registry user account
 .SS Synopsis
 .P
 .RS 2
@@ -15,7 +14,7 @@ aliases: login, add\-user
 .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 \fBnpm\-config\fP \fInpm\-config)\fR\|\.
+the default registry will be used (see npm help \fBconfig\fP)\.
 .P
 The username, password, and email are read in from prompts\.
 .P
@@ -36,13 +35,13 @@ 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 \fBnpm\-scope\fP \fI/docs/using\-npm/scope\fR\|\.
+to the scope of the project directory you're currently in, if any\. See npm help \fBscope\fP\|\.
 .SS scope
 .P
 Default: none
 .P
 If specified, the user and login credentials given will be associated
-with the specified scope\. See \fBnpm\-scope\fP \fI/docs/using\-npm/scope\fR\|\. You can use both at the same time,
+with the specified scope\. See npm help \fBscope\fP\|\. You can use both at the same time,
 e\.g\.
 .P
 .RS 2
@@ -70,9 +69,7 @@ registries\. Can be used with \fB\-\-registry\fP and / or \fB\-\-scope\fP, e\.g\
 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 \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\.
+different hostnames\. See \fBalways\-auth\fP in npm help \fBconfig\fP for more details on always\-auth\. Registry\-specific configuration of \fBalways\-auth\fP takes precedence over any global configuration\.
 .SS auth\-type
 .RS 0
 .IP \(bu 2
@@ -90,12 +87,12 @@ username/password entry in legacy npm\.
 .IP \(bu 2
 npm help registry
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
 npm help npmrc
 .IP \(bu 2
-npm help npm\-owner
+npm help owner
 .IP \(bu 2
-npm help npm\-whoami
+npm help whoami
 
 .RE
diff --git a/deps/npm/man/man1/npm-audit.1 b/deps/npm/man/man1/npm-audit.1
index 9641530e40..50e61c60d1 100644
--- a/deps/npm/man/man1/npm-audit.1
+++ b/deps/npm/man/man1/npm-audit.1
@@ -1,7 +1,6 @@
-.TH "NPM\-AUDIT" "" "November 2019" "" ""
+.TH "NPM\-AUDIT" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-audit\fR
-.SH Run a security audit
+\fBnpm-audit\fR \- Run a security audit
 .SS Synopsis
 .P
 .RS 2
@@ -165,7 +164,7 @@ configuration setting\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-install
+npm help install
 .IP \(bu 2
 npm help package\-locks
 .IP \(bu 2
diff --git a/deps/npm/man/man1/npm-bin.1 b/deps/npm/man/man1/npm-bin.1
index 157fdda28c..8a925ee708 100644
--- a/deps/npm/man/man1/npm-bin.1
+++ b/deps/npm/man/man1/npm-bin.1
@@ -1,7 +1,6 @@
-.TH "NPM\-BIN" "" "November 2019" "" ""
+.TH "NPM\-BIN" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-bin\fR
-.SH Display npm bin folder
+\fBnpm-bin\fR \- Display npm bin folder
 .SS Synopsis
 .P
 .RS 2
@@ -15,13 +14,13 @@ Print the folder where npm will install executables\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-prefix
+npm help prefix
 .IP \(bu 2
-npm help npm\-root
+npm help root
 .IP \(bu 2
 npm help folders
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
 npm help npmrc
 
diff --git a/deps/npm/man/man1/npm-bugs.1 b/deps/npm/man/man1/npm-bugs.1
index 8a11be5d79..953d83bc78 100644
--- a/deps/npm/man/man1/npm-bugs.1
+++ b/deps/npm/man/man1/npm-bugs.1
@@ -1,7 +1,6 @@
-.TH "NPM\-BUGS" "" "November 2019" "" ""
+.TH "NPM\-BUGS" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-bugs\fR
-.SH Bugs for a package in a web browser maybe
+\fBnpm-bugs\fR \- Bugs for a package in a web browser maybe
 .SS Synopsis
 .P
 .RS 2
@@ -41,18 +40,18 @@ The base URL of the npm package registry\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-docs
+npm help docs
 .IP \(bu 2
-npm help npm\-view
+npm help view
 .IP \(bu 2
-npm help npm\-publish
+npm help publish
 .IP \(bu 2
 npm help registry
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
 npm help npmrc
 .IP \(bu 2
-npm help 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 f3341bfbed..7ea0362572 100644
--- a/deps/npm/man/man1/npm-build.1
+++ b/deps/npm/man/man1/npm-build.1
@@ -1,7 +1,6 @@
-.TH "NPM\-BUILD" "" "November 2019" "" ""
+.TH "NPM\-BUILD" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-build\fR
-.SH Build a package
+\fBnpm-build\fR \- Build a package
 .SS Synopsis
 .P
 .RS 2
@@ -30,12 +29,12 @@ directly, run:
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-install
+npm help install
 .IP \(bu 2
-npm help npm\-link
+npm help link
 .IP \(bu 2
 npm help scripts
 .IP \(bu 2
-npm help 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 89a22d5a5e..8c911b2d57 100644
--- a/deps/npm/man/man1/npm-bundle.1
+++ b/deps/npm/man/man1/npm-bundle.1
@@ -1,7 +1,6 @@
-.TH "NPM\-BUNDLE" "" "November 2019" "" ""
+.TH "NPM\-BUNDLE" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-bundle\fR
-.SH REMOVED
+\fBnpm-bundle\fR \- REMOVED
 .SS Description
 .P
 The \fBnpm bundle\fP command has been removed in 1\.0, for the simple reason
@@ -12,6 +11,6 @@ Just use \fBnpm install\fP now to do what \fBnpm bundle\fP used to do\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-install
+npm help install
 
 .RE
diff --git a/deps/npm/man/man1/npm-cache.1 b/deps/npm/man/man1/npm-cache.1
index 2a54d573c7..5740233250 100644
--- a/deps/npm/man/man1/npm-cache.1
+++ b/deps/npm/man/man1/npm-cache.1
@@ -1,7 +1,6 @@
-.TH "NPM\-CACHE" "" "November 2019" "" ""
+.TH "NPM\-CACHE" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-cache\fR
-.SH Manipulates packages cache
+\fBnpm-cache\fR \- Manipulates packages cache
 .SS Synopsis
 .P
 .RS 2
@@ -77,15 +76,15 @@ The root cache folder\.
 .IP \(bu 2
 npm help folders
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
 npm help npmrc
 .IP \(bu 2
-npm help npm\-install
+npm help install
 .IP \(bu 2
-npm help npm\-publish
+npm help publish
 .IP \(bu 2
-npm help npm\-pack
+npm help pack
 .IP \(bu 2
 https://npm\.im/cacache
 .IP \(bu 2
diff --git a/deps/npm/man/man1/npm-ci.1 b/deps/npm/man/man1/npm-ci.1
index 6f93d0bc7d..adad702349 100644
--- a/deps/npm/man/man1/npm-ci.1
+++ b/deps/npm/man/man1/npm-ci.1
@@ -1,7 +1,6 @@
-.TH "NPM\-CI" "" "November 2019" "" ""
+.TH "NPM\-CI" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-ci\fR
-.SH Install a project with a clean slate
+\fBnpm-ci\fR \- Install a project with a clean slate
 .SS Synopsis
 .P
 .RS 2
@@ -46,7 +45,7 @@ cache:
 .RE
 .SS Description
 .P
-This command is similar to \fBnpm\-install\fP \fInpm\-install\fR, except it's meant to be used in
+This command is similar to npm help \fBinstall\fP, 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
@@ -71,7 +70,7 @@ It will never write to \fBpackage\.json\fP or any of the package\-locks: install
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-install
+npm help install
 .IP \(bu 2
 npm help package\-locks
 
diff --git a/deps/npm/man/man1/npm-completion.1 b/deps/npm/man/man1/npm-completion.1
index 6e0f840564..ce6654a0c9 100644
--- a/deps/npm/man/man1/npm-completion.1
+++ b/deps/npm/man/man1/npm-completion.1
@@ -1,7 +1,6 @@
-.TH "NPM\-COMPLETION" "" "November 2019" "" ""
+.TH "NPM\-COMPLETION" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-completion\fR
-.SH Tab Completion for npm
+\fBnpm-completion\fR \- Tab Completion for npm
 .SS Synopsis
 .P
 .RS 2
@@ -26,8 +25,8 @@ npm completion >> ~/\.zshrc
 .RE
 .P
 You may of course also pipe the output of \fBnpm completion\fP to a file
-such as \fB/usr/local/etc/bash_completion\.d/npm\fP or
-\fB/etc/bash_completion\.d/npm\fP if you have a system that will read
+such as \fB/usr/local/etc/bash_completion\.d/npm\fP or 
+\fB/etc/bash_completion\.d/npm\fP if you have a system that will read 
 that file for you\.
 .P
 When \fBCOMP_CWORD\fP, \fBCOMP_LINE\fP, and \fBCOMP_POINT\fP are defined in the
diff --git a/deps/npm/man/man1/npm-config.1 b/deps/npm/man/man1/npm-config.1
index 016e8c265a..423f7f258b 100644
--- a/deps/npm/man/man1/npm-config.1
+++ b/deps/npm/man/man1/npm-config.1
@@ -1,7 +1,6 @@
-.TH "NPM\-CONFIG" "" "November 2019" "" ""
+.TH "NPM\-CONFIG" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-config\fR
-.SH Manage the npm configuration files
+\fBnpm-config\fR \- Manage the npm configuration files
 .SS Synopsis
 .P
 .RS 2
@@ -22,9 +21,9 @@ aliases: c
 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 npmrc \fI/docs/configuring\-npm/npmrc\fR for more information about the npmrc files\.
+See npm help npmrc for more information about the npmrc files\.
 .P
-See config \fI/docs/using\-npm/config\fR for a more thorough discussion of the mechanisms
+See npm help config for a more thorough discussion of the mechanisms
 involved\.
 .P
 The \fBnpm config\fP command can be used to update and edit the contents
@@ -86,9 +85,9 @@ global config\.
 .IP \(bu 2
 npm help folders
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
-npm help package\-json
+npm help package\.json
 .IP \(bu 2
 npm help npmrc
 .IP \(bu 2
diff --git a/deps/npm/man/man1/npm-dedupe.1 b/deps/npm/man/man1/npm-dedupe.1
index 7795f39652..f4b0e6fd56 100644
--- a/deps/npm/man/man1/npm-dedupe.1
+++ b/deps/npm/man/man1/npm-dedupe.1
@@ -1,7 +1,6 @@
-.TH "NPM\-DEDUPE" "" "November 2019" "" ""
+.TH "NPM\-DEDUPE" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-dedupe\fR
-.SH Reduce duplication
+\fBnpm-dedupe\fR \- Reduce duplication
 .SS Synopsis
 .P
 .RS 2
@@ -30,7 +29,7 @@ a
 .fi
 .RE
 .P
-In this case, \fBnpm\-dedupe\fP will transform the tree to:
+In this case, \fBnpm dedupe\fP will transform the tree to:
 .P
 .RS 2
 .nf
@@ -62,10 +61,10 @@ result in new modules being installed\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-ls
+npm help ls
 .IP \(bu 2
-npm help npm\-update
+npm help update
 .IP \(bu 2
-npm help npm\-install
+npm help install
 
 .RE
diff --git a/deps/npm/man/man1/npm-deprecate.1 b/deps/npm/man/man1/npm-deprecate.1
index b010c33447..cfbe9dcf2b 100644
--- a/deps/npm/man/man1/npm-deprecate.1
+++ b/deps/npm/man/man1/npm-deprecate.1
@@ -1,7 +1,6 @@
-.TH "NPM\-DEPRECATE" "" "November 2019" "" ""
+.TH "NPM\-DEPRECATE" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-deprecate\fR
-.SH Deprecate a version of a package
+\fBnpm-deprecate\fR \- Deprecate a version of a package
 .SS Synopsis
 .P
 .RS 2
@@ -14,7 +13,7 @@ npm deprecate <pkg>[@<version>] <message>
 This command will update the npm registry entry for a package, providing
 a deprecation warning to all who attempt to install it\.
 .P
-It works on version ranges \fIhttps://semver\.npmjs\.com/\fR as well as specific
+It works on version ranges \fIhttps://semver\.npmjs\.com/\fR as well as specific 
 versions, so you can do something like this:
 .P
 .RS 2
@@ -26,13 +25,13 @@ npm deprecate my\-thing@"< 0\.2\.3" "critical bug fixed in v0\.2\.3"
 Note that you must be the package owner to deprecate something\.  See the
 \fBowner\fP and \fBadduser\fP help topics\.
 .P
-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
+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\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-publish
+npm help publish
 .IP \(bu 2
 npm help registry
 
diff --git a/deps/npm/man/man1/npm-dist-tag.1 b/deps/npm/man/man1/npm-dist-tag.1
index 0403e8bf67..211c02dbac 100644
--- a/deps/npm/man/man1/npm-dist-tag.1
+++ b/deps/npm/man/man1/npm-dist-tag.1
@@ -1,7 +1,6 @@
-.TH "NPM\-DIST\-TAG" "" "November 2019" "" ""
+.TH "NPM\-DIST\-TAG" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-dist-tag\fR
-.SH Modify package distribution tags
+\fBnpm-dist-tag\fR \- Modify package distribution tags
 .SS Synopsis
 .P
 .RS 2
@@ -92,15 +91,15 @@ begin with a number or the letter \fBv\fP\|\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-publish
+npm help publish
 .IP \(bu 2
-npm help npm\-install
+npm help install
 .IP \(bu 2
-npm help npm\-dedupe
+npm help dedupe
 .IP \(bu 2
 npm help registry
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
 npm help npmrc
 
diff --git a/deps/npm/man/man1/npm-docs.1 b/deps/npm/man/man1/npm-docs.1
index 09c786b72e..7adbedd9a0 100644
--- a/deps/npm/man/man1/npm-docs.1
+++ b/deps/npm/man/man1/npm-docs.1
@@ -1,7 +1,6 @@
-.TH "NPM\-DOCS" "" "November 2019" "" ""
+.TH "NPM\-DOCS" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-docs\fR
-.SH Docs for a package in a web browser maybe
+\fBnpm-docs\fR \- Docs for a package in a web browser maybe
 .SS Synopsis
 .P
 .RS 2
@@ -43,16 +42,16 @@ The base URL of the npm package registry\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-view
+npm help view
 .IP \(bu 2
-npm help npm\-publish
+npm help publish
 .IP \(bu 2
 npm help registry
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
 npm help npmrc
 .IP \(bu 2
-npm help 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 81c6aa1e90..52ccfb0c4c 100644
--- a/deps/npm/man/man1/npm-doctor.1
+++ b/deps/npm/man/man1/npm-doctor.1
@@ -1,7 +1,6 @@
-.TH "NPM\-DOCTOR" "" "November 2019" "" ""
+.TH "NPM\-DOCTOR" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-doctor\fR
-.SH Check your environments
+\fBnpm-doctor\fR \- Check your environments
 .SS Synopsis
 .P
 .RS 2
@@ -105,10 +104,10 @@ cache, you should probably run \fBnpm cache clean\fP and reset the cache\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-bugs
+npm help bugs
 .IP \(bu 2
-npm help npm\-help
+npm help help
 .IP \(bu 2
-npm help npm\-ping
+npm help ping
 
 .RE
diff --git a/deps/npm/man/man1/npm-edit.1 b/deps/npm/man/man1/npm-edit.1
index 21e6d9ffad..36abc611f8 100644
--- a/deps/npm/man/man1/npm-edit.1
+++ b/deps/npm/man/man1/npm-edit.1
@@ -1,7 +1,6 @@
-.TH "NPM\-EDIT" "" "November 2019" "" ""
+.TH "NPM\-EDIT" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-edit\fR
-.SH Edit an installed package
+\fBnpm-edit\fR \- Edit an installed package
 .SS Synopsis
 .P
 .RS 2
@@ -39,11 +38,11 @@ The command to run for \fBnpm edit\fP or \fBnpm config edit\fP\|\.
 .IP \(bu 2
 npm help folders
 .IP \(bu 2
-npm help npm\-explore
+npm help explore
 .IP \(bu 2
-npm help npm\-install
+npm help install
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
 npm help npmrc
 
diff --git a/deps/npm/man/man1/npm-explore.1 b/deps/npm/man/man1/npm-explore.1
index fa352a8ac4..5b27fcf9b7 100644
--- a/deps/npm/man/man1/npm-explore.1
+++ b/deps/npm/man/man1/npm-explore.1
@@ -1,7 +1,6 @@
-.TH "NPM\-EXPLORE" "" "November 2019" "" ""
+.TH "NPM\-EXPLORE" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-explore\fR
-.SH description: Browse an installed package
+\fBnpm-explore\fR \- Browse an installed package
 .SS Synopsis
 .P
 .RS 2
@@ -44,12 +43,12 @@ The shell to run for the \fBnpm explore\fP command\.
 .IP \(bu 2
 npm help folders
 .IP \(bu 2
-npm help npm\-edit
+npm help edit
 .IP \(bu 2
-npm help npm\-rebuild
+npm help rebuild
 .IP \(bu 2
-npm help npm\-build
+npm help build
 .IP \(bu 2
-npm help npm\-install
+npm help install
 
 .RE
diff --git a/deps/npm/man/man1/npm-fund.1 b/deps/npm/man/man1/npm-fund.1
index 4468d31269..83280693f2 100644
--- a/deps/npm/man/man1/npm-fund.1
+++ b/deps/npm/man/man1/npm-fund.1
@@ -1,7 +1,6 @@
-.TH "NPM\-FUND" "" "November 2019" "" ""
+.TH "NPM\-FUND" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-fund\fR
-.SH Retrieve funding information
+\fBnpm-fund\fR \- Retrieve funding information
 .SS Synopsis
 .P
 .RS 2
@@ -56,12 +55,12 @@ Set it to \fBfalse\fP in order to use all\-ansi output\.
 .SH See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-docs
+npm help docs
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
-npm help npm\-install
+npm help install
 .IP \(bu 2
-npm help npm\-ls
+npm help ls
 
 .RE
diff --git a/deps/npm/man/man1/npm-help-search.1 b/deps/npm/man/man1/npm-help-search.1
index bb29239dd2..01400fe152 100644
--- a/deps/npm/man/man1/npm-help-search.1
+++ b/deps/npm/man/man1/npm-help-search.1
@@ -1,7 +1,6 @@
-.TH "NPM\-HELP\-SEARCH" "" "November 2019" "" ""
+.TH "NPM\-HELP\-SEARCH" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-help-search\fR
-.SH Search npm help documentation
+\fBnpm-help-search\fR \- Search npm help documentation
 .SS Synopsis
 .P
 .RS 2
@@ -38,6 +37,6 @@ If false, then help\-search will just list out the help topics found\.
 .IP \(bu 2
 npm help npm
 .IP \(bu 2
-npm help npm\-help
+npm help help
 
 .RE
diff --git a/deps/npm/man/man1/npm-help.1 b/deps/npm/man/man1/npm-help.1
index 79849f7258..f5331a6ac7 100644
--- a/deps/npm/man/man1/npm-help.1
+++ b/deps/npm/man/man1/npm-help.1
@@ -1,7 +1,6 @@
-.TH "NPM\-HELP" "" "November 2019" "" ""
+.TH "NPM\-HELP" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-help\fR
-.SH Get help on npm
+\fBnpm-help\fR \- Get help on npm
 .SS Synopsis
 .P
 .RS 2
@@ -37,12 +36,12 @@ npm help npm
 .IP \(bu 2
 npm help folders
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
 npm help npmrc
 .IP \(bu 2
-npm help package\-json
+npm help package\.json
 .IP \(bu 2
-npm help npm\-help\-search
+npm help help\-search
 
 .RE
diff --git a/deps/npm/man/man1/npm-hook.1 b/deps/npm/man/man1/npm-hook.1
index 9cab9c6e9c..521f44f01a 100644
--- a/deps/npm/man/man1/npm-hook.1
+++ b/deps/npm/man/man1/npm-hook.1
@@ -1,7 +1,6 @@
-.TH "NPM\-HOOK" "" "November 2019" "" ""
+.TH "NPM\-HOOK" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-hook\fR
-.SH Manage registry hooks
+\fBnpm-hook\fR \- Manage registry hooks
 .SS Synopsis
 .P
 .RS 2
@@ -71,8 +70,7 @@ $ npm hook rm id\-deadbeef
 .RE
 .SS Description
 .P
-Allows you to manage npm
-hooks \fIhttps://blog\.npmjs\.org/post/145260155635/introducing\-hooks\-get\-notifications\-of\-npm\fR,
+Allows you to manage npm hooks \fIhttps://blog\.npmjs\.org/post/145260155635/introducing\-hooks\-get\-notifications\-of\-npm\fR,
 including adding, removing, listing, and updating\.
 .P
 Hooks allow you to configure URL endpoints that will be notified whenever a
diff --git a/deps/npm/man/man1/npm-init.1 b/deps/npm/man/man1/npm-init.1
index cfaa116a56..d0bf42286e 100644
--- a/deps/npm/man/man1/npm-init.1
+++ b/deps/npm/man/man1/npm-init.1
@@ -1,7 +1,6 @@
-.TH "NPM\-INIT" "" "November 2019" "" ""
+.TH "NPM\-INIT" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-init\fR
-.SH create a package\.json file
+\fBnpm-init\fR \- create a package\.json file
 .SS Synopsis
 .P
 .RS 2
@@ -82,9 +81,9 @@ will create a scoped package\.
 .IP \(bu 2
 https://github\.com/isaacs/init\-package\-json
 .IP \(bu 2
-npm help package\-json
+npm help package\.json
 .IP \(bu 2
-npm help npm\-version
+npm help version
 .IP \(bu 2
 npm help scope
 
diff --git a/deps/npm/man/man1/npm-install-ci-test.1 b/deps/npm/man/man1/npm-install-ci-test.1
index 93cdb43bec..8ac6535034 100644
--- a/deps/npm/man/man1/npm-install-ci-test.1
+++ b/deps/npm/man/man1/npm-install-ci-test.1
@@ -1,7 +1,6 @@
 .TH "NPM" "" "November 2019" "" ""
 .SH "NAME"
 \fBnpm\fR
-.SH Install a project with a clean slate and run tests
 .SS Synopsis
 .P
 .RS 2
@@ -17,8 +16,8 @@ This command runs an \fBnpm ci\fP followed immediately by an \fBnpm test\fP\|\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-ci
+npm help ci
 .IP \(bu 2
-npm help npm\-test
+npm help test
 
 .RE
diff --git a/deps/npm/man/man1/npm-install-test.1 b/deps/npm/man/man1/npm-install-test.1
index 6df1508f1a..470d20f357 100644
--- a/deps/npm/man/man1/npm-install-test.1
+++ b/deps/npm/man/man1/npm-install-test.1
@@ -1,7 +1,6 @@
 .TH "NPM" "" "November 2019" "" ""
 .SH "NAME"
 \fBnpm\fR
-.SH Install package(s) and run tests
 .SS Synopsis
 .P
 .RS 2
@@ -26,8 +25,8 @@ takes exactly the same arguments as \fBnpm install\fP\|\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-install
+npm help install
 .IP \(bu 2
-npm help npm\-test
+npm help test
 
 .RE
diff --git a/deps/npm/man/man1/npm-install.1 b/deps/npm/man/man1/npm-install.1
index 564c306cad..c3ab9dc774 100644
--- a/deps/npm/man/man1/npm-install.1
+++ b/deps/npm/man/man1/npm-install.1
@@ -1,7 +1,6 @@
-.TH "NPM\-INSTALL" "" "November 2019" "" ""
+.TH "NPM\-INSTALL" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-install\fR
-.SH Install a package
+\fBnpm-install\fR \- Install a package
 .SS Synopsis
 .P
 .RS 2
@@ -11,6 +10,7 @@ npm install [<@scope>/]<name>
 npm install [<@scope>/]<name>@<tag>
 npm install [<@scope>/]<name>@<version>
 npm install [<@scope>/]<name>@<version range>
+npm install <alias>@npm:<name>
 npm install <git\-host>:<git\-user>/<repo\-name>
 npm install <git repo url>
 npm install <tarball file>
@@ -26,20 +26,20 @@ common options: [\-P|\-\-save\-prod|\-D|\-\-save\-dev|\-O|\-\-save\-optional] [\
 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 package\-lock\.json \fI/docs/configuring\-npm/package\-lock\.json\fR and \fBnpm\-shrinkwrap\fP \fInpm\-shrinkwrap\fR\|\.
+files exist\. See npm help package\-lock\.json and npm help \fBshrinkwrap\fP\|\.
 .P
 A \fBpackage\fP is:
 .RS 0
 .IP \(bu 2
-a) a folder containing a program described by a \fBpackage\.json\fP \fI/docs/configuring\-npm/package\-json\fR file
+a) a folder containing a program described by a npm help \fBpackage\.json\fP 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 \fBnpm\-registry\fP \fInpm\-registry)\fR with (c)
+d) a \fB<name>@<version>\fP that is published on the registry (see npm help \fBregistry\fP) with (c)
 .IP \(bu 2
-e) a \fB<name>@<tag>\fP (see \fBnpm\-dist\-tag\fP \fInpm\-dist\-tag)\fR that points to (d)
+e) a \fB<name>@<tag>\fP (see npm help \fBdist\-tag\fP) that points to (d)
 .IP \(bu 2
 f) a \fB<name>\fP that has a "latest" tag satisfying (e)
 .IP \(bu 2
@@ -59,10 +59,12 @@ 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 \fBpackage\.json\fP \fI/docs/configuring\-npm/package\-json\fR\|\.
+  in npm help \fBpackage\.json\fP\|\.
   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\|\.
+  \fBdevDependencies\fP\|\. To install all modules listed in both \fBdependencies\fP 
+  and \fBdevDependencies\fP when \fBNODE_ENV\fP environment variable is set to \fBproduction\fP, 
+  you can use \fB\-\-production=false\fP\|\.
 .QP
 NOTE: The \fB\-\-production\fP flag has no particular meaning when adding a
   dependency to a project\.
@@ -111,7 +113,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
-  \fBnpm\-config\fP \fI/docs/using\-npm/config\fR\|\. The config's default value is \fBlatest\fP\|\.)
+  npm help \fBconfig\fP\|\. 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:
@@ -121,44 +123,66 @@ npm install \./package\.tgz
     npm install sax
 .fi
 .RE
-  \fBnpm install\fP saves any specified packages into \fBdependencies\fP by default\.
-  Additionally, you can control where and how they get saved with some
-  additional flags:
-.RS
 .IP \(bu 2
-\fB\-P, \-\-save\-prod\fP: Package will appear in your \fBdependencies\fP\|\. This is the
+\fBnpm install <alias>@npm:<name>\fP:
+  Install a package under a custom alias\. Allows multiple versions of
+  a same\-name package side\-by\-side, more convenient import names for
+  packages with otherwise long ones and using git forks replacements
+  or forked npm packages as replacements\. Aliasing works only on your
+  project and does not rename packages in transitive dependencies\.
+  Aliases should follow the naming conventions stated in
+  \fBvalidate\-npm\-package\-name\fP \fIhttps://www\.npmjs\.com/package/validate\-npm\-package\-name#naming\-rules\fR\|\.
+  Examples:
 .P
 .RS 2
 .nf
-               default unless `\-D` or `\-O` are present\.
+    npm install my\-react@npm:react
+    npm install jquery2@npm:jquery@2
+    npm install jquery3@npm:jquery@3
+    npm install npa@npm:npm\-package\-arg
 .fi
 .RE
-.IP \(bu 2
-\fB\-D, \-\-save\-dev\fP: Package will appear in your \fBdevDependencies\fP\|\.
-.IP \(bu 2
-\fB\-O, \-\-save\-optional\fP: Package will appear in your \fBoptionalDependencies\fP\|\.
-.IP \(bu 2
-\fB\-\-no\-save\fP: Prevents saving to \fBdependencies\fP\|\.
+
+.RE
+.P
+.RS 2
+.nf
+`npm install` saves any specified packages into `dependencies` by default\.
+Additionally, you can control where and how they get saved with some
+additional flags:
+
+* `\-P, \-\-save\-prod`: Package will appear in your `dependencies`\. This is the
+                     default unless `\-D` or `\-O` are present\.
+
+* `\-D, \-\-save\-dev`: Package will appear in your `devDependencies`\.
+
+* `\-O, \-\-save\-optional`: Package will appear in your `optionalDependencies`\.
+
+* `\-\-no\-save`: Prevents saving to `dependencies`\.
+
 When using any of the above options to save dependencies to your
 package\.json, there are two additional, optional flags:
-.IP \(bu 2
-\fB\-E, \-\-save\-exact\fP: Saved dependencies will be configured with an
-exact version rather than using npm's default semver range
-operator\.
-.IP \(bu 2
-\fB\-B, \-\-save\-bundle\fP: Saved dependencies will also be added to your \fBbundleDependencies\fP list\.
-Further, if you have an \fBnpm\-shrinkwrap\.json\fP or \fBpackage\-lock\.json\fP then it
+
+* `\-E, \-\-save\-exact`: Saved dependencies will be configured with an
+  exact version rather than using npm's default semver range
+  operator\.
+
+* `\-B, \-\-save\-bundle`: Saved dependencies will also be added to your `bundleDependencies` list\.
+
+Further, if you have an `npm\-shrinkwrap\.json` or `package\-lock\.json` then it
 will be updated as well\.
-\fB<scope>\fP is optional\. The package will be downloaded from the registry
+
+`<scope>` 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 \fBnpm\-scope\fP \fI/docs/using\-npm/scope\fR\|\.
+the given scope the default registry is assumed\. See npm help `scope`\.
+
 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\.
+
 Examples:
-.P
-.RS 2
-.nf
+
+```bash
 npm install sax
 npm install githubname/reponame
 npm install @myorg/privatepackage
@@ -166,14 +190,14 @@ npm install node\-tap \-\-save\-dev
 npm install dtrace\-provider \-\-save\-optional
 npm install readable\-stream \-\-save\-exact
 npm install ansi\-regex \-\-save\-bundle
-.fi
-.RE
-.IP \(bu 2
-\fINote*\fR: If there is a file or folder named \fB<name>\fP in the current
+```
+
+**Note**: If there is a file or folder named `<name>` 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\.
@@ -202,7 +226,7 @@ fetch the package by name if it is not valid\.
 .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 \fBpackage\.json\fP \fI/docs/configuring\-npm/package\-json\fR\|\.
+  will follow the same rules for resolving dependencies described in npm help \fBpackage\.json\fP\|\.
   Note that most version ranges must be put in quotes so that your shell will
   treat it as a single argument\.
   Example:
@@ -378,11 +402,11 @@ npm install sax \-\-force
 .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
+install that acknowledges the number of dependencies looking for funding\.
+See \fBnpm\-fund(1)\fP
 .P
 The \fB\-g\fP or \fB\-\-global\fP argument will cause npm to install the package globally
-rather than locally\.  See npm\-folders \fI/docs/configuring\-npm/folders\fR\|\.
+rather than locally\.  See npm help folders\.
 .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
@@ -391,7 +415,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 \fBnpm\-scripts\fP \fI/docs/using\-npm/scripts\fR\|\.
+scripts defined in the package\.json\. See npm help \fBscripts\fP\|\.
 .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,7 +446,7 @@ The \fB\-\-only={prod[uction]|dev[elopment]}\fP argument will cause either only
 The \fB\-\-no\-audit\fP argument can be used to disable sending of audit reports to
 the configured registries\.  See \fBnpm\-audit\fP \fInpm\-audit\fR for details on what is sent\.
 .P
-See \fBnpm\-config\fP \fI/docs/using\-npm/config\fR\|\.  Many of the configuration params have some
+See npm help \fBconfig\fP\|\.  Many of the configuration params have some
 effect on installation, since that's most of what npm does\.
 .SS Algorithm
 .P
@@ -476,8 +500,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\-folders \fI/docs/configuring\-npm/folders\fR for a more detailed description of the specific
-folder structures that npm creates\.
+See npm help folders for a more detailed description of the specific folder structures that npm creates\.
 .SS Limitations of npm's Install Algorithm
 .P
 npm will refuse to install any package with an identical name to the
@@ -511,32 +534,32 @@ affects a real use\-case, it will be investigated\.
 .IP \(bu 2
 npm help folders
 .IP \(bu 2
-npm help npm\-update
+npm help update
 .IP \(bu 2
-npm help npm\-audit
+npm help audit
 .IP \(bu 2
-npm help npm\-fund
+npm help fund
 .IP \(bu 2
-npm help npm\-link
+npm help link
 .IP \(bu 2
-npm help npm\-rebuild
+npm help rebuild
 .IP \(bu 2
 npm help scripts
 .IP \(bu 2
-npm help npm\-build
+npm help build
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
 npm help npmrc
 .IP \(bu 2
 npm help registry
 .IP \(bu 2
-npm help npm\-dist\-tag
+npm help dist\-tag
 .IP \(bu 2
-npm help npm\-uninstall
+npm help uninstall
 .IP \(bu 2
-npm help npm\-shrinkwrap
+npm help shrinkwrap
 .IP \(bu 2
-npm help 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 b107c897d3..3485c81745 100644
--- a/deps/npm/man/man1/npm-link.1
+++ b/deps/npm/man/man1/npm-link.1
@@ -1,7 +1,6 @@
-.TH "NPM\-LINK" "" "November 2019" "" ""
+.TH "NPM\-LINK" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-link\fR
-.SH Symlink a package folder
+\fBnpm-link\fR \- Symlink a package folder
 .SS Synopsis
 .P
 .RS 2
@@ -28,7 +27,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 \fBnpm\-scope\fP \fInpm\-scope\fR\|\.
+The package name can be optionally prefixed with a scope\. See npm help \fBscope\fP\|\.
 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
@@ -77,8 +76,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 \fBnpm\-scope\fP \fInpm\-scope)\fR your link command must
-include that scope, e\.g\.
+If your linked package is scoped (see npm help \fBscope\fP) your link command must include that scope, e\.g\.
 .P
 .RS 2
 .nf
@@ -90,13 +88,13 @@ npm link @myorg/privatepackage
 .IP \(bu 2
 npm help developers
 .IP \(bu 2
-npm help package\-json
+npm help package\.json
 .IP \(bu 2
-npm help npm\-install
+npm help npm\- nstall
 .IP \(bu 2
 npm help folders
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
 npm help npmrc
 
diff --git a/deps/npm/man/man1/npm-logout.1 b/deps/npm/man/man1/npm-logout.1
index 27e9b73293..997668379c 100644
--- a/deps/npm/man/man1/npm-logout.1
+++ b/deps/npm/man/man1/npm-logout.1
@@ -1,7 +1,6 @@
-.TH "NPM\-LOGOUT" "" "November 2019" "" ""
+.TH "NPM\-LOGOUT" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-logout\fR
-.SH Log out of the registry
+\fBnpm-logout\fR \- Log out of the registry
 .SS Synopsis
 .P
 .RS 2
@@ -32,7 +31,7 @@ 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 \fBnpm\-scope\fP \fInpm\-scope\fR\|\.
+If specified, you will be logged out of the specified scope\. See npm help \fBscope\fP\|\.
 .P
 .RS 2
 .nf
@@ -42,12 +41,12 @@ npm logout \-\-scope=@myco
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-adduser
+npm help adduser
 .IP \(bu 2
 npm help registry
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
-npm help npm\-whoami
+npm help whoami
 
 .RE
diff --git a/deps/npm/man/man1/npm-ls.1 b/deps/npm/man/man1/npm-ls.1
index 2574e9ede2..c6d035446f 100644
--- a/deps/npm/man/man1/npm-ls.1
+++ b/deps/npm/man/man1/npm-ls.1
@@ -1,7 +1,6 @@
-.TH "NPM\-LS" "" "November 2019" "" ""
+.TH "NPM\-LS" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-ls\fR
-.SH List installed packages
+\fBnpm-ls\fR \- List installed packages
 .SS Synopsis
 .P
 .RS 2
@@ -23,7 +22,7 @@ For example, running \fBnpm ls promzard\fP in npm's source tree will show:
 .P
 .RS 2
 .nf
-    npm@6\.13\.0 /path/to/npm
+    npm@6\.13\.1 /path/to/npm
     └─┬ init\-package\-json@0\.0\.4
       └── promzard@0\.1\.5
 .fi
@@ -143,20 +142,20 @@ Set it to false in order to use all\-ansi output\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
 npm help npmrc
 .IP \(bu 2
 npm help folders
 .IP \(bu 2
-npm help npm\-install
+npm help install
 .IP \(bu 2
-npm help npm\-link
+npm help link
 .IP \(bu 2
-npm help npm\-prune
+npm help prune
 .IP \(bu 2
-npm help npm\-outdated
+npm help outdated
 .IP \(bu 2
-npm help npm\-update
+npm help update
 
 .RE
diff --git a/deps/npm/man/man1/npm-org.1 b/deps/npm/man/man1/npm-org.1
index 67d3ebb47c..d3e7cb74f5 100644
--- a/deps/npm/man/man1/npm-org.1
+++ b/deps/npm/man/man1/npm-org.1
@@ -1,7 +1,6 @@
-.TH "NPM\-ORG" "" "November 2019" "" ""
+.TH "NPM\-ORG" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-org\fR
-.SH Manage orgs
+\fBnpm-org\fR \- Manage orgs
 .SS Synopsis
 .P
 .RS 2
diff --git a/deps/npm/man/man1/npm-outdated.1 b/deps/npm/man/man1/npm-outdated.1
index 93db219519..681b457d8d 100644
--- a/deps/npm/man/man1/npm-outdated.1
+++ b/deps/npm/man/man1/npm-outdated.1
@@ -1,7 +1,6 @@
-.TH "NPM\-OUTDATED" "" "November 2019" "" ""
+.TH "NPM\-OUTDATED" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-outdated\fR
-.SH Check for outdated packages
+\fBnpm-outdated\fR \- Check for outdated packages
 .SS Synopsis
 .P
 .RS 2
@@ -146,9 +145,9 @@ Max depth for checking dependency tree\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-update
+npm help update
 .IP \(bu 2
-npm help npm\-dist\-tag
+npm help dist\-tag
 .IP \(bu 2
 npm help registry
 .IP \(bu 2
diff --git a/deps/npm/man/man1/npm-owner.1 b/deps/npm/man/man1/npm-owner.1
index 66a84f8be3..343fcc3ea3 100644
--- a/deps/npm/man/man1/npm-owner.1
+++ b/deps/npm/man/man1/npm-owner.1
@@ -1,7 +1,6 @@
-.TH "NPM\-OWNER" "" "November 2019" "" ""
+.TH "NPM\-OWNER" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-owner\fR
-.SH Manage package owners
+\fBnpm-owner\fR \- Manage package owners
 .SS Synopsis
 .P
 .RS 2
@@ -42,11 +41,11 @@ with \fB\-\-otp\fP\|\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-publish
+npm help publish
 .IP \(bu 2
 npm help registry
 .IP \(bu 2
-npm help npm\-adduser
+npm help adduser
 .IP \(bu 2
 npm help disputes
 
diff --git a/deps/npm/man/man1/npm-pack.1 b/deps/npm/man/man1/npm-pack.1
index d035679478..9b8feaaa67 100644
--- a/deps/npm/man/man1/npm-pack.1
+++ b/deps/npm/man/man1/npm-pack.1
@@ -1,7 +1,6 @@
-.TH "NPM\-PACK" "" "November 2019" "" ""
+.TH "NPM\-PACK" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-pack\fR
-.SH Create a tarball from a package
+\fBnpm-pack\fR \- Create a tarball from a package
 .SS Synopsis
 .P
 .RS 2
@@ -27,11 +26,11 @@ actually packing anything\. Reports on what would have gone into the tarball\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-cache
+npm help cache
 .IP \(bu 2
-npm help npm\-publish
+npm help publish
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
 npm help npmrc
 
diff --git a/deps/npm/man/man1/npm-ping.1 b/deps/npm/man/man1/npm-ping.1
index 27df33858b..dda31466bf 100644
--- a/deps/npm/man/man1/npm-ping.1
+++ b/deps/npm/man/man1/npm-ping.1
@@ -1,7 +1,6 @@
-.TH "NPM\-PING" "" "November 2019" "" ""
+.TH "NPM\-PING" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-ping\fR
-.SH Ping npm registry
+\fBnpm-ping\fR \- Ping npm registry
 .SS Synopsis
 .P
 .RS 2
@@ -30,7 +29,7 @@ Ping error: {*Detail about error}
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
 npm help npmrc
 
diff --git a/deps/npm/man/man1/npm-prefix.1 b/deps/npm/man/man1/npm-prefix.1
index d08fc57b73..04d7c00ecf 100644
--- a/deps/npm/man/man1/npm-prefix.1
+++ b/deps/npm/man/man1/npm-prefix.1
@@ -1,7 +1,6 @@
-.TH "NPM\-PREFIX" "" "November 2019" "" ""
+.TH "NPM\-PREFIX" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-prefix\fR
-.SH Display prefix
+\fBnpm-prefix\fR \- Display prefix
 .SS Synopsis
 .P
 .RS 2
@@ -16,17 +15,17 @@ to contain a \fBpackage\.json\fP file or \fBnode_modules\fP directory, unless \f
 also specified\.
 .P
 If \fB\-g\fP is specified, this will be the value of the global prefix\. See
-\fBnpm\-config\fP \fInpm\-config\fR for more detail\.
+npm help \fBconfig\fP for more detail\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-root
+npm help root
 .IP \(bu 2
-npm help npm\-bin
+npm help bin
 .IP \(bu 2
 npm help folders
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
 npm help npmrc
 
diff --git a/deps/npm/man/man1/npm-profile.1 b/deps/npm/man/man1/npm-profile.1
index c19738ca7b..d05b776e85 100644
--- a/deps/npm/man/man1/npm-profile.1
+++ b/deps/npm/man/man1/npm-profile.1
@@ -38,6 +38,6 @@ available on non npmjs\.com registries\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-config
+npm help config
 
 .RE
diff --git a/deps/npm/man/man1/npm-prune.1 b/deps/npm/man/man1/npm-prune.1
index 64a790fe7b..58ccd7b385 100644
--- a/deps/npm/man/man1/npm-prune.1
+++ b/deps/npm/man/man1/npm-prune.1
@@ -1,7 +1,6 @@
-.TH "NPM\-PRUNE" "" "November 2019" "" ""
+.TH "NPM\-PRUNE" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-prune\fR
-.SH Remove extraneous packages
+\fBnpm-prune\fR \- Remove extraneous packages
 .SS Synopsis
 .P
 .RS 2
@@ -37,10 +36,10 @@ and it's up to you to run \fBnpm prune\fP from time\-to\-time to remove them\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-uninstall
+npm help uninstall
 .IP \(bu 2
 npm help folders
 .IP \(bu 2
-npm help npm\-ls
+npm help ls
 
 .RE
diff --git a/deps/npm/man/man1/npm-publish.1 b/deps/npm/man/man1/npm-publish.1
index 410be8799b..45de41045e 100644
--- a/deps/npm/man/man1/npm-publish.1
+++ b/deps/npm/man/man1/npm-publish.1
@@ -1,7 +1,6 @@
-.TH "NPM\-PUBLISH" "" "November 2019" "" ""
+.TH "NPM\-PUBLISH" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-publish\fR
-.SH Publish a package
+\fBnpm-publish\fR \- Publish a package
 .SS Synopsis
 .P
 .RS 2
@@ -18,12 +17,10 @@ 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
-\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\.
+npm help \fBdevelopers\fP 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 \fBnpm\-scope\fP \fInpm\-scope\fR in the name
-(see \fBpackage\.json\fP \fI/docs/configuring\-npm/package\-json)\fR\|\.
+specifying a different default registry or using a npm help \fBscope\fP in the name (see npm help \fBpackage\.json\fP)\.
 .RS 0
 .IP \(bu 2
 \fB<folder>\fP:
@@ -61,13 +58,13 @@ 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 \fBnpm\-unpublish\fP \fInpm\-unpublish\fR\|\.
+it is removed with npm help \fBunpublish\fP\|\.
 .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 \fBnpm\-pack\fP \fInpm\-pack\fR, which figures out the files to be
+Similar to \fB\-\-dry\-run\fP see npm help \fBpack\fP, which figures out the files to be
 included and packs them into a tarball to be uploaded to the registry\.
 .SS See Also
 .RS 0
@@ -76,16 +73,16 @@ npm help registry
 .IP \(bu 2
 npm help scope
 .IP \(bu 2
-npm help npm\-adduser
+npm help adduser
 .IP \(bu 2
-npm help npm\-owner
+npm help owner
 .IP \(bu 2
-npm help npm\-deprecate
+npm help deprecate
 .IP \(bu 2
-npm help npm\-dist\-tag
+npm help dist\-tag
 .IP \(bu 2
-npm help npm\-pack
+npm help pack
 .IP \(bu 2
-npm help npm\-profile
+npm help profile
 
 .RE
diff --git a/deps/npm/man/man1/npm-rebuild.1 b/deps/npm/man/man1/npm-rebuild.1
index e0b0975d17..49674eca38 100644
--- a/deps/npm/man/man1/npm-rebuild.1
+++ b/deps/npm/man/man1/npm-rebuild.1
@@ -1,7 +1,6 @@
-.TH "NPM\-REBUILDD" "" "November 2019" "" ""
+.TH "NPM\-REBUILD" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-rebuildd\fR
-.SH Rebuild a package
+\fBnpm-rebuild\fR \- Rebuild a package
 .SS Synopsis
 .P
 .RS 2
@@ -13,14 +12,12 @@ alias: npm rb
 .RE
 .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\.
+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\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-build
+npm help build
 .IP \(bu 2
-npm help npm\-install
+npm help install
 
 .RE
diff --git a/deps/npm/man/man1/npm-repo.1 b/deps/npm/man/man1/npm-repo.1
index c0e3e5e92b..597292b8d4 100644
--- a/deps/npm/man/man1/npm-repo.1
+++ b/deps/npm/man/man1/npm-repo.1
@@ -1,7 +1,6 @@
-.TH "NPM\-REPO" "" "November 2019" "" ""
+.TH "NPM\-REPO" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-repo\fR
-.SH Open package repository page in the browser
+\fBnpm-repo\fR \- Open package repository page in the browser
 .SS Synopsis
 .P
 .RS 2
@@ -29,8 +28,8 @@ The browser that is called by the \fBnpm repo\fP command to open websites\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-docs
+npm help docs
 .IP \(bu 2
-npm help npm\-config
+npm help config
 
 .RE
diff --git a/deps/npm/man/man1/npm-restart.1 b/deps/npm/man/man1/npm-restart.1
index 3c62324faf..9d566ef0c2 100644
--- a/deps/npm/man/man1/npm-restart.1
+++ b/deps/npm/man/man1/npm-restart.1
@@ -1,7 +1,6 @@
-.TH "NPM\-RESTART" "" "November 2019" "" ""
+.TH "NPM\-RESTART" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-restart\fR
-.SH Restart a package
+\fBnpm-restart\fR \- Restart a package
 .SS Synopsis
 .P
 .RS 2
@@ -46,16 +45,16 @@ behavior will be accompanied by an increase in major version number
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-run\-script
+npm help run\-script
 .IP \(bu 2
-npm help /docs/using\-npm/scripts
+npm help scripts
 .IP \(bu 2
-npm help npm\-test
+npm help test
 .IP \(bu 2
-npm help npm\-start
+npm help start
 .IP \(bu 2
-npm help npm\-stop
+npm help stop
 .IP \(bu 2
-npm help npm\-restart
+npm help restart
 
 .RE
diff --git a/deps/npm/man/man1/npm-root.1 b/deps/npm/man/man1/npm-root.1
index a50ff39e3f..f86181ef7c 100644
--- a/deps/npm/man/man1/npm-root.1
+++ b/deps/npm/man/man1/npm-root.1
@@ -1,7 +1,6 @@
-.TH "NPM\-ROOT" "" "November 2019" "" ""
+.TH "NPM\-ROOT" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-root\fR
-.SH Display npm root
+\fBnpm-root\fR \- Display npm root
 .SS Synopsis
 .P
 .RS 2
@@ -15,13 +14,13 @@ Print the effective \fBnode_modules\fP folder to standard out\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-prefix
+npm help prefix
 .IP \(bu 2
-npm help npm\-bin
+npm help bin
 .IP \(bu 2
 npm help folders
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
 npm help npmrc
 
diff --git a/deps/npm/man/man1/npm-run-script.1 b/deps/npm/man/man1/npm-run-script.1
index 0896b9a8b3..22c9f95306 100644
--- a/deps/npm/man/man1/npm-run-script.1
+++ b/deps/npm/man/man1/npm-run-script.1
@@ -1,7 +1,6 @@
-.TH "NPM\-RUN\-SCRIPT" "" "November 2019" "" ""
+.TH "NPM\-RUN\-SCRIPT" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-run-script\fR
-.SH Run arbitrary package scripts
+\fBnpm-run-script\fR \- Run arbitrary package scripts
 .SS Synopsis
 .P
 .RS 2
@@ -92,14 +91,14 @@ without breaking the execution chain\.
 .IP \(bu 2
 npm help scripts
 .IP \(bu 2
-npm help npm\-test
+npm help test
 .IP \(bu 2
-npm help npm\-start
+npm help start
 .IP \(bu 2
-npm help npm\-restart
+npm help restart
 .IP \(bu 2
-npm help npm\-stop
+npm help stop
 .IP \(bu 2
-npm help npm\-config
+npm help config
 
 .RE
diff --git a/deps/npm/man/man1/npm-search.1 b/deps/npm/man/man1/npm-search.1
index 037081c81a..b792f39e81 100644
--- a/deps/npm/man/man1/npm-search.1
+++ b/deps/npm/man/man1/npm-search.1
@@ -1,7 +1,6 @@
-.TH "NPM\-SEARCH" "" "November 2019" "" ""
+.TH "NPM\-SEARCH" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-search\fR
-.SH Search for packages
+\fBnpm-search\fR \- Search for packages
 .SS Synopsis
 .P
 .RS 2
@@ -127,10 +126,10 @@ setting\.
 .IP \(bu 2
 npm help registry
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
 npm help npmrc
 .IP \(bu 2
-npm help npm\-view
+npm help view
 
 .RE
diff --git a/deps/npm/man/man1/npm-shrinkwrap.1 b/deps/npm/man/man1/npm-shrinkwrap.1
index e5aa6917a9..33286dc895 100644
--- a/deps/npm/man/man1/npm-shrinkwrap.1
+++ b/deps/npm/man/man1/npm-shrinkwrap.1
@@ -1,7 +1,6 @@
-.TH "NPM\-SHRINKWRAP" "" "November 2019" "" ""
+.TH "NPM\-SHRINKWRAP" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-shrinkwrap\fR
-.SH Lock down dependency versions for publication
+\fBnpm-shrinkwrap\fR \- Lock down dependency versions for publication
 .SS Synopsis
 .P
 .RS 2
@@ -15,24 +14,24 @@ 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\-package\-locks \fInpm\-package\-locks\fR\|\.
+of package locks in npm, see npm help package\-locks\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-install
+npm help install
 .IP \(bu 2
-npm help npm\-run\-script
+npm help run\-script
 .IP \(bu 2
 npm help scripts
 .IP \(bu 2
-npm help package\-json
+npm help package\.js
 .IP \(bu 2
 npm help package\-locks
 .IP \(bu 2
-npm help package\-lock\-json
+npm help package\-lock\.json
 .IP \(bu 2
-npm help shrinkwrap\-json
+npm help shrinkwrap\.json
 .IP \(bu 2
-npm help npm\-ls
+npm help ls
 
 .RE
diff --git a/deps/npm/man/man1/npm-star.1 b/deps/npm/man/man1/npm-star.1
index 5aafda481f..4ad11a7efb 100644
--- a/deps/npm/man/man1/npm-star.1
+++ b/deps/npm/man/man1/npm-star.1
@@ -1,7 +1,6 @@
-.TH "NPM\-STAR" "" "November 2019" "" ""
+.TH "NPM\-STAR" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-star\fR
-.SH Mark your favorite packages
+\fBnpm-star\fR \- Mark your favorite packages
 .SS Synopsis
 .P
 .RS 2
@@ -21,10 +20,10 @@ It's a boolean thing\.  Starring repeatedly has no additional effect\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-view
+npm help view
 .IP \(bu 2
-npm help npm\-whoami
+npm help whoami
 .IP \(bu 2
-npm help npm\-adduser
+npm help adduser
 
 .RE
diff --git a/deps/npm/man/man1/npm-stars.1 b/deps/npm/man/man1/npm-stars.1
index f68edfa96b..2c7b6f2430 100644
--- a/deps/npm/man/man1/npm-stars.1
+++ b/deps/npm/man/man1/npm-stars.1
@@ -1,7 +1,6 @@
-.TH "NPM\-STARS" "" "November 2019" "" ""
+.TH "NPM\-STARS" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-stars\fR
-.SH View packages marked as favorites
+\fBnpm-stars\fR \- View packages marked as favorites
 .SS Synopsis
 .P
 .RS 2
@@ -19,12 +18,12 @@ you will most certainly enjoy this command\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-star
+npm help star
 .IP \(bu 2
-npm help npm\-view
+npm help view
 .IP \(bu 2
-npm help npm\-whoami
+npm help whoami
 .IP \(bu 2
-npm help npm\-adduser
+npm help adduser
 
 .RE
diff --git a/deps/npm/man/man1/npm-start.1 b/deps/npm/man/man1/npm-start.1
index 72e59dedae..e83e6800f7 100644
--- a/deps/npm/man/man1/npm-start.1
+++ b/deps/npm/man/man1/npm-start.1
@@ -1,7 +1,6 @@
-.TH "NPM\-START" "" "November 2019" "" ""
+.TH "NPM\-START" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-start\fR
-.SH Start a package
+\fBnpm-start\fR \- Start a package
 .SS Synopsis
 .P
 .RS 2
@@ -16,19 +15,18 @@ 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 \fBnpm\-run\-script\fP \fInpm\-run\-script\fR for
-more details\.
+use custom arguments when executing scripts\. Refer to npm help \fBrun\-script\fP for more details\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-run\-script
+npm help run\-script
 .IP \(bu 2
 npm help scripts
 .IP \(bu 2
-npm help npm\-test
+npm help test
 .IP \(bu 2
-npm help npm\-restart
+npm help restart
 .IP \(bu 2
-npm help npm\-stop
+npm help stop
 
 .RE
diff --git a/deps/npm/man/man1/npm-stop.1 b/deps/npm/man/man1/npm-stop.1
index a2f6d92cfe..d3b612b08a 100644
--- a/deps/npm/man/man1/npm-stop.1
+++ b/deps/npm/man/man1/npm-stop.1
@@ -1,7 +1,6 @@
-.TH "NPM\-STOP" "" "November 2019" "" ""
+.TH "NPM\-STOP" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-stop\fR
-.SH Stop a package
+\fBnpm-stop\fR \- Stop a package
 .SS Synopsis
 .P
 .RS 2
@@ -15,14 +14,14 @@ This runs a package's "stop" script, if one was provided\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-run\-script
+npm help run\-script
 .IP \(bu 2
 npm help scripts
 .IP \(bu 2
-npm help npm\-test
+npm help test
 .IP \(bu 2
-npm help npm\-start
+npm help start
 .IP \(bu 2
-npm help npm\-restart
+npm help restart
 
 .RE
diff --git a/deps/npm/man/man1/npm-team.1 b/deps/npm/man/man1/npm-team.1
index 94fb186a19..ca7f0beb1f 100644
--- a/deps/npm/man/man1/npm-team.1
+++ b/deps/npm/man/man1/npm-team.1
@@ -1,7 +1,6 @@
-.TH "NPM\-TEAM" "" "November 2019" "" ""
+.TH "NPM\-TEAM" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-team\fR
-.SH Manage organization teams and team memberships
+\fBnpm-team\fR \- Manage organization teams and team memberships
 .SS Synopsis
 .P
 .RS 2
@@ -23,13 +22,11 @@ Used to manage teams in organizations, and change team memberships\. Does not
 handle permissions for packages\.
 .P
 Teams must always be fully qualified with the organization/scope they belong to
-when operating on them, separated by a colon (\fB:\fP)\. That is, if you have a
-\fBdevelopers\fP team on a \fBfoo\fP organization, you must always refer to that team as
-\fBfoo:developers\fP in these commands\.
+when operating on them, separated by a colon (\fB:\fP)\. That is, if you have a \fBwombats\fP team in a \fBwisdom\fP organization, you must always refer to that team as \fBwisdom:wombats\fP in these commands\.
 .RS 0
 .IP \(bu 2
 create / destroy:
-Create a new team, or destroy an existing one\.
+Create a new team, or destroy an existing one\. Note: You cannot remove the \fBdevelopers\fP team, <a href="https://docs\.npmjs\.com/about\-developers\-team" target="_blank">learn more\.</a>
 .IP \(bu 2
 add / rm:
 Add a user to an existing team, or remove a user from a team they belong to\.
@@ -60,7 +57,7 @@ use the \fBnpm access\fP command to grant or revoke the appropriate permissions\
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-access
+npm help access
 .IP \(bu 2
 npm help registry
 
diff --git a/deps/npm/man/man1/npm-test.1 b/deps/npm/man/man1/npm-test.1
index c3d18a3eed..bd18fedb50 100644
--- a/deps/npm/man/man1/npm-test.1
+++ b/deps/npm/man/man1/npm-test.1
@@ -1,7 +1,6 @@
-.TH "NPM\-TEST" "" "November 2019" "" ""
+.TH "NPM\-TEST" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-test\fR
-.SH Test a package
+\fBnpm-test\fR \- Test a package
 .SS Synopsis
 .P
 .RS 2
@@ -17,14 +16,14 @@ This runs a package's "test" script, if one was provided\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-run\-script
+npm help run\-script
 .IP \(bu 2
 npm help scripts
 .IP \(bu 2
-npm help npm\-start
+npm help start
 .IP \(bu 2
-npm help npm\-restart
+npm help restart
 .IP \(bu 2
-npm help npm\-stop
+npm help stop
 
 .RE
diff --git a/deps/npm/man/man1/npm-token.1 b/deps/npm/man/man1/npm-token.1
index f52451cae0..04a0f5f82f 100644
--- a/deps/npm/man/man1/npm-token.1
+++ b/deps/npm/man/man1/npm-token.1
@@ -6,7 +6,7 @@
 \fBnpm token revoke <token|id>\fP:
 This removes an authentication token, making it immediately unusable\. This can accept
 both complete tokens (as you get back from \fBnpm token create\fP and will
-find in your \fB\|\.npmrc\fP) and ids as seen in the \fBnpm token list\fP output\.
+find in your \fB\|\.npmrc\fP) and ids as seen in the \fBnpm token list\fP output\. 
 This will NOT accept the truncated token found in \fBnpm token list\fP output\.
 
 .RE
diff --git a/deps/npm/man/man1/npm-uninstall.1 b/deps/npm/man/man1/npm-uninstall.1
index 4be083e6f8..35523df7a1 100644
--- a/deps/npm/man/man1/npm-uninstall.1
+++ b/deps/npm/man/man1/npm-uninstall.1
@@ -1,7 +1,6 @@
-.TH "NPM\-UNINSTALL" "" "November 2019" "" ""
+.TH "NPM\-UNINSTALL" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-uninstall\fR
-.SH Remove a package
+\fBnpm-uninstall\fR \- Remove a package
 .SS Synopsis
 .P
 .RS 2
@@ -44,7 +43,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 \fBnpm\-scope\fP \fIsnpm\-scope\fR\|\.
+Scope is optional and follows the usual rules for npm help \fBscope\fP\|\.
 .P
 Examples:
 .P
@@ -60,13 +59,13 @@ npm uninstall lodash \-\-no\-save
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-prune
+npm help prune
 .IP \(bu 2
-npm help npm\-install
+npm help install
 .IP \(bu 2
 npm help folders
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
 npm help npmrc
 
diff --git a/deps/npm/man/man1/npm-unpublish.1 b/deps/npm/man/man1/npm-unpublish.1
index 5e2f8dac49..f0ce9fa92d 100644
--- a/deps/npm/man/man1/npm-unpublish.1
+++ b/deps/npm/man/man1/npm-unpublish.1
@@ -1,7 +1,6 @@
-.TH "NPM\-UNPUBLISH" "" "November 2019" "" ""
+.TH "NPM\-UNPUBLISH" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-unpublish\fR
-.SH Remove a package from the registry
+\fBnpm-unpublish\fR \- Remove a package from the registry
 .SS Synopsis
 .P
 .RS 2
@@ -37,18 +36,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 \fBnpm\-scope\fP \fI/docs/using\-npm/scope\fR\|\.
+The scope is optional and follows the usual rules for npm help \fBscope\fP\|\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-deprecate
+npm help deprecate
 .IP \(bu 2
-npm help npm\-publish
+npm help publish
 .IP \(bu 2
 npm help registry
 .IP \(bu 2
-npm help npm\-adduser
+npm help adduser
 .IP \(bu 2
-npm help npm\-owner
+npm help owner
 
 .RE
diff --git a/deps/npm/man/man1/npm-update.1 b/deps/npm/man/man1/npm-update.1
index 3b78a687e2..2ebe4a2945 100644
--- a/deps/npm/man/man1/npm-update.1
+++ b/deps/npm/man/man1/npm-update.1
@@ -1,7 +1,6 @@
-.TH "NPM\-UPDATE" "" "November 2019" "" ""
+.TH "NPM\-UPDATE" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-update\fR
-.SH Update a package
+\fBnpm-update\fR \- Update a package
 .SS Synopsis
 .P
 .RS 2
@@ -30,8 +29,8 @@ As of \fBnpm@2\.6\.1\fP, the \fBnpm update\fP will only inspect top\-level packa
 Prior versions of \fBnpm\fP would also recursively inspect all dependencies\.
 To get the old behavior, use \fBnpm \-\-depth 9999 update\fP\|\.
 .P
-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,
+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\|\.
 .SS Example
 .P
@@ -128,16 +127,16 @@ be \fIdowngraded\fR\|\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-install
+npm help install
 .IP \(bu 2
-npm help npm\-outdated
+npm help outdated
 .IP \(bu 2
-npm help npm\-shrinkwrap
+npm help shrinkwrap
 .IP \(bu 2
 npm help registry
 .IP \(bu 2
 npm help folders
 .IP \(bu 2
-npm help npm\-ls
+npm help ls
 
 .RE
diff --git a/deps/npm/man/man1/npm-version.1 b/deps/npm/man/man1/npm-version.1
index 42f6bee330..df14c7f67e 100644
--- a/deps/npm/man/man1/npm-version.1
+++ b/deps/npm/man/man1/npm-version.1
@@ -1,7 +1,6 @@
-.TH "NPM\-VERSION" "" "November 2019" "" ""
+.TH "NPM\-VERSION" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-version\fR
-.SH Bump a package version
+\fBnpm-version\fR \- Bump a package version
 .SS Synopsis
 .P
 .RS 2
@@ -110,7 +109,7 @@ Type: Boolean
 
 .RE
 .P
-Prevents throwing an error when \fBnpm version\fP is used to set the new version
+Prevents throwing an error when \fBnpm version\fP is used to set the new version 
 to the same value as the current version\.
 .SS git\-tag\-version
 .RS 0
@@ -147,13 +146,13 @@ Note that you must have a default GPG key set up in your git config for this to
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-init
+npm help init
 .IP \(bu 2
-npm help npm\-run\-script
+npm help run\-script
 .IP \(bu 2
 npm help scripts
 .IP \(bu 2
-package\.json \fI/docs/configuring\-npm/package\-json\fR
+npm help package\.json
 .IP \(bu 2
 npm help semver
 .IP \(bu 2
diff --git a/deps/npm/man/man1/npm-view.1 b/deps/npm/man/man1/npm-view.1
index 156fd1eae0..72d41b9cf1 100644
--- a/deps/npm/man/man1/npm-view.1
+++ b/deps/npm/man/man1/npm-view.1
@@ -1,7 +1,6 @@
-.TH "NPM\-VIEW" "" "November 2019" "" ""
+.TH "NPM\-VIEW" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-view\fR
-.SH View registry info
+\fBnpm-view\fR \- View registry info
 .SS Synopsis
 .P
 .RS 2
@@ -89,7 +88,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 \fBpackage\.json\fP \fI/docs/configuring\-npm/package\.json\fR for more on this\.)
+the shortened string format\.  (See npm help \fBpackage\.json\fP for more on this\.)
 .P
 .RS 2
 .nf
@@ -131,14 +130,14 @@ the field name\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-search
+npm help search
 .IP \(bu 2
 npm help registry
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
 npm help npmrc
 .IP \(bu 2
-npm help npm\-docs
+npm help docs
 
 .RE
diff --git a/deps/npm/man/man1/npm-whoami.1 b/deps/npm/man/man1/npm-whoami.1
index ea09d40c02..40c627e8c4 100644
--- a/deps/npm/man/man1/npm-whoami.1
+++ b/deps/npm/man/man1/npm-whoami.1
@@ -1,7 +1,6 @@
-.TH "NPM\-WHOAMI" "" "November 2019" "" ""
+.TH "NPM\-WHOAMI" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-whoami\fR
-.SH Display npm username
+\fBnpm-whoami\fR \- Display npm username
 .SS Synopsis
 .P
 .RS 2
@@ -15,10 +14,10 @@ Print the \fBusername\fP config to standard output\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
 npm help npmrc
 .IP \(bu 2
-npm help npm\-adduser
+npm help adduser
 
 .RE
diff --git a/deps/npm/man/man1/npm.1 b/deps/npm/man/man1/npm.1
index 525990c758..6ef81e0318 100644
--- a/deps/npm/man/man1/npm.1
+++ b/deps/npm/man/man1/npm.1
@@ -1,7 +1,6 @@
-.TH "NPM" "" "November 2019" "" ""
+.TH "NPM" "1" "November 2019" "" ""
 .SH "NAME"
-\fBnpm\fR
-.SH javascript package manager
+\fBnpm\fR \- javascript package manager
 .SS Synopsis
 .P
 .RS 2
@@ -11,7 +10,7 @@ npm <command> [args]
 .RE
 .SS Version
 .P
-6\.13\.0
+6\.13\.1
 .SS Description
 .P
 npm is the package manager for the Node JavaScript platform\.  It puts
@@ -37,7 +36,7 @@ terms of use\.
 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
-\fBnpm\-install\fP \fInpm\-install\fR for more info\.  It can do a lot of stuff\.
+npm help \fBinstall\fP 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\.
@@ -58,7 +57,7 @@ the node\-gyp repository \fIhttps://github\.com/TooTallNate/node\-gyp\fR and
 the node\-gyp Wiki \fIhttps://github\.com/TooTallNate/node\-gyp/wiki\fR\|\.
 .SS Directories
 .P
-See \fBnpm\-folders\fP \fI/docs/configuring\-npm/folders\fR to learn about where npm puts stuff\.
+See npm help \fBfolders\fP to learn about where npm puts stuff\.
 .P
 In particular, npm has two modes of operation:
 .RS 0
@@ -83,7 +82,7 @@ following help topics:
 .RS 0
 .IP \(bu 2
 json:
-Make a package\.json file\.  See \fBpackage\.json\fP \fI/docs/configuring\-npm/package\.json\fR\|\.
+Make a package\.json file\.  See npm help \fBpackage\.json\fP\|\.
 .IP \(bu 2
 link:
 For linking your current working code into Node's path, so that you
@@ -136,7 +135,7 @@ lib/utils/config\-defs\.js\.  These must not be changed\.
 
 .RE
 .P
-See \fBnpm\-config\fP \fI/docs/using\-npm/config\fR for much much more information\.
+See npm help \fBconfig\fP for much much more information\.
 .SS Contributions
 .P
 Patches welcome!
@@ -147,9 +146,7 @@ the contributing guidelines and check the issues list\.
 .IP \(bu 2
 CONTRIBUTING\.md \fIhttps://github\.com/npm/cli/blob/latest/CONTRIBUTING\.md\fR
 .IP \(bu 2
-Bug tracker \fIhttps://npm\.community/c/bugs\fR
-.IP \(bu 2
-Support tracker \fIhttps://npm\.community/c/support\fR
+Bug tracker \fIhttps://github\.com/npm/cli/issues\fR
 
 .RE
 .SS Bugs
@@ -175,13 +172,13 @@ i@izs\.me
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-help
+npm help help
 .IP \(bu 2
-npm help package\-json
+npm help package\.json
 .IP \(bu 2
-npm help npm\-install
+npm help install
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
 npm help npmrc
 
diff --git a/deps/npm/man/man1/npx.1 b/deps/npm/man/man1/npx.1
index d00c489c39..cd44dda044 100644
--- a/deps/npm/man/man1/npx.1
+++ b/deps/npm/man/man1/npx.1
@@ -172,3 +172,4 @@ This work is released by its authors into the public domain under CC0\-1\.0\. Se
 \fBnpm\-config(7)\fP
 
 .RE
+
diff --git a/deps/npm/man/man5/folders.5 b/deps/npm/man/man5/folders.5
index 6654212195..a6d8027759 100644
--- a/deps/npm/man/man5/folders.5
+++ b/deps/npm/man/man5/folders.5
@@ -31,24 +31,24 @@ not be included in the package tarball\.
 .P
 This allows a package maintainer to install all of their dependencies
 (and dev dependencies) locally, but only re\-publish those items that
-cannot be found elsewhere\.  See \fBpackage\.json\fP \fI/docs/configuring\-npm/package\.json\fR for more information\.
+cannot be found elsewhere\.  See npm help \fBpackage\.json\fP for more information\.
 .SS See also
 .RS 0
 .IP \(bu 2
-npm help package\-json
+npm help package\.json
 .IP \(bu 2
-npm help npm\-install
+npm help install
 .IP \(bu 2
-npm help npm\-pack
+npm help pack
 .IP \(bu 2
-npm help npm\-cache
+npm help cache
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
 npm help npmrc
 .IP \(bu 2
 npm help config
 .IP \(bu 2
-npm help npm\-publish
+npm help publish
 
 .RE
diff --git a/deps/npm/man/man5/install.5 b/deps/npm/man/man5/install.5
index 6c74ccd297..d14b649fe7 100644
--- a/deps/npm/man/man5/install.5
+++ b/deps/npm/man/man5/install.5
@@ -1,6 +1,7 @@
-.TH "DOWNLOAD" "" "November 2019" "" ""
+.TH "INSTALL" "5" "November 2019" "" ""
 .SH "NAME"
-\fBDownload\fR
+\fBinstall\fR \- Download and Install npm
+.SS Description
 .P
 To publish and install packages to and from the public npm registry, you must install Node\.js and the npm command line interface using either a Node version manager or a Node installer\. \fBWe strongly recommend using a Node version manager to install Node\.js and npm\.\fR We do not recommend using a Node installer, since the Node installation process installs npm in a directory with local permissions and can cause permissions errors when you run npm packages globally\.
 .SS Overview
diff --git a/deps/npm/man/man5/npmrc.5 b/deps/npm/man/man5/npmrc.5
index 651a515697..d11cb449c0 100644
--- a/deps/npm/man/man5/npmrc.5
+++ b/deps/npm/man/man5/npmrc.5
@@ -1,7 +1,6 @@
-.TH "NPMRC" "" "November 2019" "" ""
+.TH "NPMRC" "5" "November 2019" "" ""
 .SH "NAME"
-\fBnpmrc\fR
-.SH The npm config files
+\fBnpmrc\fR \- The npm config files
 .SS Description
 .P
 npm gets its config settings from the command line, environment
@@ -10,7 +9,7 @@ variables, and \fBnpmrc\fP files\.
 The \fBnpm config\fP command can be used to update and edit the contents
 of the user and global npmrc files\.
 .P
-For a list of available configuration options, see npm\-config \fI/docs/using\-npm/config\fR\|\.
+For a list of available configuration options, see npm help config\.
 .SS Files
 .P
 The four relevant files are:
@@ -98,11 +97,11 @@ manner\.
 .IP \(bu 2
 npm help folders
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
 npm help config
 .IP \(bu 2
-npm help package\-json
+npm help package\.json
 .IP \(bu 2
 npm help npm
 
diff --git a/deps/npm/man/man5/package-json.5 b/deps/npm/man/man5/package-json.5
index 959b744fd7..01350c6410 100644
--- a/deps/npm/man/man5/package-json.5
+++ b/deps/npm/man/man5/package-json.5
@@ -1,14 +1,13 @@
-.TH "PACKAGE\.JSON" "" "November 2019" "" ""
+.TH "PACKAGE\.JSON" "5" "November 2019" "" ""
 .SH "NAME"
-\fBpackage.json\fR
-.SH Specifics of npm's package\.json handling
+\fBpackage.json\fR \- Specifics of npm's package\.json handling
 .SS Description
 .P
 This document is all you need to know about what's required in your package\.json
 file\.  It must be actual JSON, not just a JavaScript object literal\.
 .P
 A lot of the behavior described in this document is affected by the config
-settings described in \fBnpm\-config\fP \fI/docs/using\-npm/config\fR\|\.
+settings described in npm help \fBconfig\fP\|\.
 .SS name
 .P
 If you plan to publish your package, the \fImost\fR important things in your
@@ -25,7 +24,7 @@ Some rules:
 The name must be less than or equal to 214 characters\. This includes the scope for
 scoped packages\.
 .IP \(bu 2
-The name can't start with a dot or an underscore\.
+The names of scoped packages can begin with a dot or an underscore\. This is not permitted without a scope\.
 .IP \(bu 2
 New packages must not have uppercase letters in the name\.
 .IP \(bu 2
@@ -52,7 +51,7 @@ already, before you get too attached to it\. https://www\.npmjs\.com/
 .RE
 .P
 A name can be optionally prefixed by a scope, e\.g\. \fB@myorg/mypackage\fP\|\. See
-\fBnpm\-scope\fP \fI/docs/using\-npm/scope\fR for more detail\.
+npm help \fBscope\fP for more detail\.
 .SS version
 .P
 If you plan to publish your package, the \fImost\fR important things in your
@@ -65,7 +64,7 @@ Version must be parseable by
 node\-semver \fIhttps://github\.com/isaacs/node\-semver\fR, which is bundled
 with npm as a dependency\.  (\fBnpm install semver\fP to use it yourself\.)
 .P
-More on version numbers and ranges at semver \fI/docs/using\-npm/semver\fR\|\.
+More on version numbers and ranges at npm help semver\.
 .SS description
 .P
 Put a description in it\.  It's a string\.  This helps people discover your
@@ -522,7 +521,7 @@ The "scripts" property is a dictionary containing script commands that are run
 at various times in the lifecycle of your package\.  The key is the lifecycle
 event, and the value is the command to run at that point\.
 .P
-See \fBnpm\-scripts\fP \fI/docs/using\-npm/scripts\fR to find out more about writing package scripts\.
+See npm help \fBscripts\fP to find out more about writing package scripts\.
 .SS config
 .P
 A "config" object can be used to set configuration parameters used in package
@@ -540,7 +539,7 @@ and then had a "start" command that then referenced the
 \fBnpm_package_config_port\fP environment variable, then the user could
 override that by doing \fBnpm config set foo:port 8001\fP\|\.
 .P
-See \fBnpm\-config\fP \fI/docs/using\-npm/config\fR and \fBnpm\-scripts\fP \fI/docs/using\-npm/scripts\fR for more on package
+See npm help \fBconfig\fP and npm help \fBscripts\fP for more on package
 configs\.
 .SS dependencies
 .P
@@ -552,7 +551,7 @@ tarball or git URL\.
 \fBPlease do not put test harnesses or transpilers in your
 \fBdependencies\fP object\.\fR  See \fBdevDependencies\fP, below\.
 .P
-See semver \fI/docs/using\-npm/semver\fR for more details about specifying version ranges\.
+See npm help semver for more details about specifying version ranges\.
 .RS 0
 .IP \(bu 2
 \fBversion\fP Must match \fBversion\fP exactly
@@ -565,9 +564,9 @@ See semver \fI/docs/using\-npm/semver\fR for more details about specifying versi
 .IP \(bu 2
 \fB<=version\fP
 .IP \(bu 2
-\fB~version\fP "Approximately equivalent to version"  See semver \fI/docs/using\-npm/semver\fR
+\fB~version\fP "Approximately equivalent to version"  See npm help semver
 .IP \(bu 2
-\fB^version\fP "Compatible with version"  See semver \fI/docs/using\-npm/semver\fR
+\fB^version\fP "Compatible with version"  See npm help semver
 .IP \(bu 2
 \fB1\.2\.x\fP 1\.2\.0, 1\.2\.1, etc\., but not 1\.3\.0
 .IP \(bu 2
@@ -585,7 +584,7 @@ See semver \fI/docs/using\-npm/semver\fR for more details about specifying versi
 .IP \(bu 2
 \fBuser/repo\fP See 'GitHub URLs' below
 .IP \(bu 2
-\fBtag\fP A specific version tagged and published as \fBtag\fP  See \fBnpm\-dist\-tag\fP \fI/docs/cli\-commands/npm\-dist\-tag\fR
+\fBtag\fP A specific version tagged and published as \fBtag\fP  See npm help \fBdist\-tag\fP
 .IP \(bu 2
 \fBpath/path/path\fP See Local Paths \fI#local\-paths\fR below
 
@@ -711,7 +710,7 @@ object\.
 .P
 These things will be installed when doing \fBnpm link\fP or \fBnpm install\fP
 from the root of a package, and can be managed like any other npm
-configuration param\.  See \fBnpm\-config\fP \fI/docs/using\-npm/config\fR for more on the topic\.
+configuration param\.  See npm help \fBconfig\fP for more on the topic\.
 .P
 For build steps that are not platform\-specific, such as compiling
 CoffeeScript or other languages to JavaScript, use the \fBprepare\fP
@@ -957,7 +956,7 @@ to the global public registry or that a scoped module is private by default\.
 Any config values can be overridden, but only "tag", "registry" and "access"
 probably matter for the purposes of publishing\.
 .P
-See \fBnpm\-config\fP \fI/docs/using\-npm/config\fR to see the list of config options that can be
+See npm help \fBconfig\fP to see the list of config options that can be
 overridden\.
 .SS DEFAULT VALUES
 .P
@@ -984,18 +983,18 @@ ignored\.
 .IP \(bu 2
 npm help semver
 .IP \(bu 2
-npm help npm\-init
+npm help init
 .IP \(bu 2
-npm help npm\-version
+npm help version
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
-npm help npm\-help
+npm help help
 .IP \(bu 2
-npm help npm\-install
+npm help install
 .IP \(bu 2
-npm help npm\-publish
+npm help publish
 .IP \(bu 2
-npm help npm\-uninstall
+npm help uninstall
 
 .RE
diff --git a/deps/npm/man/man5/package-lock-json.5 b/deps/npm/man/man5/package-lock-json.5
index 075e07985a..36dbbc4023 100644
--- a/deps/npm/man/man5/package-lock-json.5
+++ b/deps/npm/man/man5/package-lock-json.5
@@ -1,7 +1,6 @@
-.TH "PACKAGE\-LOCK\.JSON" "" "November 2019" "" ""
+.TH "PACKAGE\-LOCK\.JSON" "5" "November 2019" "" ""
 .SH "NAME"
-\fBpackage-lock.json\fR
-.SH A manifestation of the manifest
+\fBpackage-lock.json\fR \- A manifestation of the manifest
 .SS Description
 .P
 \fBpackage\-lock\.json\fP is automatically generated for any operations where npm
@@ -25,7 +24,7 @@ And optimize the installation process by allowing npm to skip repeated metadata
 .P
 One key detail about \fBpackage\-lock\.json\fP is that it cannot be published, and it
 will be ignored if found in any place other than the toplevel package\. It shares
-a format with npm\-shrinkwrap\.json \fIdocs/configuring\-npm/shrinkwrap\-json\fR, which is essentially the same file, but
+a format with npm help npm\-shrinkwrap\.json, which is essentially the same file, but
 allows publication\. This is not recommended unless deploying a CLI tool or
 otherwise using the publication process for producing production packages\.
 .P
@@ -140,14 +139,14 @@ The dependencies of this dependency, exactly as at the top level\.
 .SS See also
 .RS 0
 .IP \(bu 2
-npm help npm\-shrinkwrap
+npm help shrinkwrap
 .IP \(bu 2
-npm help shrinkwrap\-json
+npm help shrinkwrap\.json
 .IP \(bu 2
 npm help package\-locks
 .IP \(bu 2
-npm help package\-json
+npm help package\.json
 .IP \(bu 2
-npm help npm\-install
+npm help install
 
 .RE
diff --git a/deps/npm/man/man5/package-locks.5 b/deps/npm/man/man5/package-locks.5
index 1a3be5255b..ea2e51fc69 100644
--- a/deps/npm/man/man5/package-locks.5
+++ b/deps/npm/man/man5/package-locks.5
@@ -1,10 +1,9 @@
-.TH "PACKAGE\-LOCKS" "" "November 2019" "" ""
+.TH "PACKAGE\-LOCKS" "5" "November 2019" "" ""
 .SH "NAME"
-\fBpackage-locks\fR
-.SH An explanation of npm lockfiles
+\fBpackage-locks\fR \- An explanation of npm lockfiles
 .SS Description
 .P
-Conceptually, the "input" to \fBnpm\-install\fP \fI/docs/cli\-commands/npm\-install\fR is a package\.json \fI/docs/configuring\-npm/package\-json\fR, while its
+Conceptually, the "input" to npm help \fBinstall\fP is a npm help package\.json, while its
 "output" is a fully\-formed \fBnode_modules\fP tree: a representation of the
 dependencies you declared\. In an ideal world, npm would work like a pure
 function: the same \fBpackage\.json\fP should produce the exact same \fBnode_modules\fP
@@ -91,8 +90,7 @@ author are not the same person, there's no way for A's author to say
 that he or she does not want to pull in newly published versions of C
 when B hasn't changed at all\.
 .P
-To prevent this potential issue, npm uses package\-lock\.json \fI/docs/configuring\-npm/package\-lock\-json\fR or, if present,
-npm\-shrinkwrap\.json \fIshrinkwrap\.json\fR\|\. These files are called package locks, or lockfiles\.
+To prevent this potential issue, npm uses npm help package\-lock\.json or, if present, npm help npm\-shrinkwrap\.json\. These files are called package locks, or lockfiles\.
 .P
 Whenever you run \fBnpm install\fP, npm generates or updates your package lock,
 which will look something like this:
@@ -122,7 +120,7 @@ which will look something like this:
 This file describes an \fIexact\fR, and more importantly \fIreproducible\fR
 \fBnode_modules\fP tree\. Once it's present, any future installation will base its
 work off this file, instead of recalculating dependency versions off
-package\.json \fI/docs/configuring\-npm/package\-json\fR\|\.
+npm help package\.json\.
 .P
 The presence of a package lock changes the installation behavior such that:
 .RS 0
@@ -191,12 +189,12 @@ pre\-\fBnpm@5\.7\.0\fP versions of npm 5, albeit a bit more noisily\. Note that
 .IP \(bu 2
 https://medium\.com/@sdboyer/so\-you\-want\-to\-write\-a\-package\-manager\-4ae9c17d9527
 .IP \(bu 2
-npm help package\-json
+npm help package\.json
 .IP \(bu 2
-npm help package\-lock\-json
+npm help package\-lock\.json
 .IP \(bu 2
-npm help shrinkwrap\-json
+npm help shrinkwrap\.json
 .IP \(bu 2
-npm help npm\-shrinkwrap
+npm help shrinkwrap
 
 .RE
diff --git a/deps/npm/man/man5/shrinkwrap-json.5 b/deps/npm/man/man5/shrinkwrap-json.5
index 8e8ba9244a..5c1e05f8b7 100644
--- a/deps/npm/man/man5/shrinkwrap-json.5
+++ b/deps/npm/man/man5/shrinkwrap-json.5
@@ -1,10 +1,9 @@
-.TH "NPM\-SHRINKWRAP\.JSON" "" "November 2019" "" ""
+.TH "NPM\-SHRINKWRAP\.JSON" "5" "November 2019" "" ""
 .SH "NAME"
-\fBnpm-shrinkwrap.json\fR
-.SH A publishable lockfile
+\fBnpm-shrinkwrap.json\fR \- A publishable lockfile
 .SS Description
 .P
-\fBnpm\-shrinkwrap\.json\fP is a file created by \fBnpm\-shrinkwrap\fP \fI/docs/cli\-commands/npm\-shrinkwrap\fR\|\. It is identical to
+\fBnpm\-shrinkwrap\.json\fP is a file created by npm help \fBshrinkwrap\fP\|\. It is identical to
 \fBpackage\-lock\.json\fP, with one major caveat: Unlike \fBpackage\-lock\.json\fP,
 \fBnpm\-shrinkwrap\.json\fP may be included when publishing a package\.
 .P
@@ -18,16 +17,16 @@ Additionally, if both \fBpackage\-lock\.json\fP and \fBnpm\-shrinkwrap\.json\fP
 in a package root, \fBpackage\-lock\.json\fP will be ignored in favor of this file\.
 .P
 For full details and description of the \fBnpm\-shrinkwrap\.json\fP file format, refer
-to the manual page for package\-lock\.json \fI/docs/configuring\-npm/package\-lock\-json\fR\|\.
+to the manual page for npm help package\-lock\.json\.
 .SS See also
 .RS 0
 .IP \(bu 2
-npm help npm\-shrinkwrap
+npm help shrinkwrap
 .IP \(bu 2
-npm help package\-lock\-json
+npm help package\-lock\.json
 .IP \(bu 2
-npm help package\-json
+npm help package\.json
 .IP \(bu 2
-npm help npm\-install
+npm help install
 
 .RE
diff --git a/deps/npm/man/man7/coding-style.7 b/deps/npm/man/man7/coding-style.7
deleted file mode 100644
index 90faff3f9d..0000000000
--- a/deps/npm/man/man7/coding-style.7
+++ /dev/null
@@ -1,222 +0,0 @@
-.TH "CODING\-STYLE" "" "November 2019" "" ""
-.SH "NAME"
-\fBcoding-style\fR
-.SH npm's "funny" coding style
-.SS Description
-.P
-npm's coding style is a bit unconventional\.  It is not different for
-difference's sake, but rather a carefully crafted style that is
-designed to reduce visual clutter and make bugs more apparent\.
-.P
-If you want to contribute to npm (which is very encouraged), you should
-make your code conform to npm's style\.
-.P
-Note: this concerns npm's code not the specific packages that you can download from the npm registry\.
-.SS Line Length
-.P
-Keep lines shorter than 80 characters\.  It's better for lines to be
-too short than to be too long\.  Break up long lists, objects, and other
-statements onto multiple lines\.
-.SS Indentation
-.P
-Two\-spaces\.  Tabs are better, but they look like hell in web browsers
-(and on GitHub), and node uses 2 spaces, so that's that\.
-.P
-Configure your editor appropriately\.
-.SS Curly braces
-.P
-Curly braces belong on the same line as the thing that necessitates them\.
-.P
-Bad:
-.P
-.RS 2
-.nf
-function ()
-{
-.fi
-.RE
-.P
-Good:
-.P
-.RS 2
-.nf
-function () {
-.fi
-.RE
-.P
-If a block needs to wrap to the next line, use a curly brace\.  Don't
-use it if it doesn't\.
-.P
-Bad:
-.P
-.RS 2
-.nf
-if (foo) { bar() }
-while (foo)
-  bar()
-.fi
-.RE
-.P
-Good:
-.P
-.RS 2
-.nf
-if (foo) bar()
-while (foo) {
-  bar()
-}
-.fi
-.RE
-.SS Semicolons
-.P
-Don't use them except in four situations:
-.RS 0
-.IP \(bu 2
-\fBfor (;;)\fP loops\.  They're actually required\.
-.IP \(bu 2
-null loops like: \fBwhile (something) ;\fP (But you'd better have a good
-reason for doing that\.)
-.IP \(bu 2
-\fBcase 'foo': doSomething(); break\fP
-.IP \(bu 2
-In front of a leading \fB(\fP or \fB[\fP at the start of the line\.
-This prevents the expression from being interpreted
-as a function call or property access, respectively\.
-
-.RE
-.P
-Some examples of good semicolon usage:
-.P
-.RS 2
-.nf
-;(x || y)\.doSomething()
-;[a, b, c]\.forEach(doSomething)
-for (var i = 0; i < 10; i ++) {
-  switch (state) {
-    case 'begin': start(); continue
-    case 'end': finish(); break
-    default: throw new Error('unknown state')
-  }
-  end()
-}
-.fi
-.RE
-.P
-Note that starting lines with \fB\-\fP and \fB+\fP also should be prefixed
-with a semicolon, but this is much less common\.
-.SS Comma First
-.P
-If there is a list of things separated by commas, and it wraps
-across multiple lines, put the comma at the start of the next
-line, directly below the token that starts the list\.  Put the
-final token in the list on a line by itself\.  For example:
-.P
-.RS 2
-.nf
-var magicWords = [ 'abracadabra'
-                 , 'gesundheit'
-                 , 'ventrilo'
-                 ]
-  , spells = { 'fireball' : function () { setOnFire() }
-             , 'water' : function () { putOut() }
-             }
-  , a = 1
-  , b = 'abc'
-  , etc
-  , somethingElse
-.fi
-.RE
-.SS Quotes
-.P
-Use single quotes for strings except to avoid escaping\.
-.P
-Bad:
-.P
-.RS 2
-.nf
-var notOk = "Just double quotes"
-.fi
-.RE
-.P
-Good:
-.P
-.RS 2
-.nf
-var ok = 'String contains "double" quotes'
-var alsoOk = "String contains 'single' quotes or apostrophe"
-.fi
-.RE
-.SS Whitespace
-.P
-Put a single space in front of \fB(\fP for anything other than a function call\.
-Also use a single space wherever it makes things more readable\.
-.P
-Don't leave trailing whitespace at the end of lines\.  Don't indent empty
-lines\.  Don't use more spaces than are helpful\.
-.SS Functions
-.P
-Use named functions\.  They make stack traces a lot easier to read\.
-.SS Callbacks, Sync/async Style
-.P
-Use the asynchronous/non\-blocking versions of things as much as possible\.
-It might make more sense for npm to use the synchronous fs APIs, but this
-way, the fs and http and child process stuff all uses the same callback\-passing
-methodology\.
-.P
-The callback should always be the last argument in the list\.  Its first
-argument is the Error or null\.
-.P
-Be very careful never to ever ever throw anything\.  It's worse than useless\.
-Just send the error message back as the first argument to the callback\.
-.SS Errors
-.P
-Always create a new Error object with your message\.  Don't just return a
-string message to the callback\.  Stack traces are handy\.
-.SS Logging
-.P
-Logging is done using the npmlog \fIhttps://github\.com/npm/npmlog\fR
-utility\.
-.P
-Please clean up logs when they are no longer helpful\.  In particular,
-logging the same object over and over again is not helpful\.  Logs should
-report what's happening so that it's easier to track down where a fault
-occurs\.
-.P
-Use appropriate log levels\.  See \fBnpm\-config\fP \fI/docs/using\-npm/config\fR and search for
-"loglevel"\.
-.SS Case, naming, etc\.
-.P
-Use \fBlowerCamelCase\fP for multiword identifiers when they refer to objects,
-functions, methods, properties, or anything not specified in this section\.
-.P
-Use \fBUpperCamelCase\fP for class names (things that you'd pass to "new")\.
-.P
-Use \fBall\-lower\-hyphen\-css\-case\fP for multiword filenames and config keys\.
-.P
-Use named functions\.  They make stack traces easier to follow\.
-.P
-Use \fBCAPS_SNAKE_CASE\fP for constants, things that should never change
-and are rarely used\.
-.P
-Use a single uppercase letter for function names where the function
-would normally be anonymous, but needs to call itself recursively\.  It
-makes it clear that it's a "throwaway" function\.
-.SS null, undefined, false, 0
-.P
-Boolean variables and functions should always be either \fBtrue\fP or
-\fBfalse\fP\|\.  Don't set it to 0 unless it's supposed to be a number\.
-.P
-When something is intentionally missing or removed, set it to \fBnull\fP\|\.
-.P
-Don't set things to \fBundefined\fP\|\.  Reserve that value to mean "not yet
-set to anything\."
-.P
-Boolean objects are forbidden\.
-.SS See Also
-.RS 0
-.IP \(bu 2
-npm help developers
-.IP \(bu 2
-npm help npm
-
-.RE
diff --git a/deps/npm/man/man7/config.7 b/deps/npm/man/man7/config.7
index c03745a3da..617b5354c1 100644
--- a/deps/npm/man/man7/config.7
+++ b/deps/npm/man/man7/config.7
@@ -301,7 +301,7 @@ for updates immediately even for fresh package data\.
 .SS prefix
 .RS 0
 .IP \(bu 2
-Default: see npm\-folders \fI/docs/configuring\-npm/folders\fR
+Default: see npm help folders
 .IP \(bu 2
 Type: path
 
@@ -793,7 +793,7 @@ Type: Boolean
 .RE
 .P
 Set to show short usage output (like the \-H output)
-instead of complete help when doing \fBnpm\-help\fP \fI/docs/cli\-commands/npm\-help\fR\|\.
+instead of complete help when doing npm help \fBhelp\fP\|\.
 .SS user
 .RS 0
 .IP \(bu 2
@@ -879,7 +879,7 @@ Set to \fB"browser"\fP to view html help content in the default web browser\.
 .SS See also
 .RS 0
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
 npm help npmrc
 .IP \(bu 2
diff --git a/deps/npm/man/man7/developers.7 b/deps/npm/man/man7/developers.7
index cfce9ce46f..2f24215d26 100644
--- a/deps/npm/man/man7/developers.7
+++ b/deps/npm/man/man7/developers.7
@@ -1,7 +1,6 @@
-.TH "DEVELOPERS" "" "November 2019" "" ""
+.TH "DEVELOPERS" "7" "November 2019" "" ""
 .SH "NAME"
-\fBdevelopers\fR
-.SH Developer Guide
+\fBdevelopers\fR \- Developer Guide
 .SS Description
 .P
 So, you've decided to use npm to develop (and maybe publish/deploy)
@@ -60,7 +59,7 @@ an argument to \fBgit checkout\fP\|\.  The default is \fBmaster\fP\|\.
 You need to have a \fBpackage\.json\fP file in the root of your project to do
 much of anything with npm\.  That is basically the whole interface\.
 .P
-See \fBpackage\.json\fP \fI/docs/configuring\-npm/package\-json\fR for details about what goes in that file\.  At the very
+See npm help \fBpackage\.json\fP for details about what goes in that file\.  At the very
 least, you need:
 .RS 0
 .IP \(bu 2
@@ -88,7 +87,7 @@ scripts:
 If you have a special compilation or installation script, then you
 should put it in the \fBscripts\fP object\.  You should definitely have at
 least a basic smoke\-test command as the "scripts\.test" field\.
-See npm\-scripts \fI/docs/using\-npm/scripts\fR\|\.
+See npm help scripts\.
 .IP \(bu 2
 main:
 If you have a single module that serves as the entry point to your
@@ -103,7 +102,7 @@ they'll get installed just like these ones\.
 .RE
 .P
 You can use \fBnpm init\fP in the root of your package in order to get you
-started with a pretty basic package\.json file\.  See \fBnpm\-init\fP \fI/docs/cli\-commands/npm\-init\fR for
+started with a pretty basic package\.json file\.  See npm help \fBinit\fP for
 more info\.
 .SS Keeping files \fIout\fR of your package
 .P
@@ -195,7 +194,7 @@ changes in real time without having to keep re\-installing it\.  (You do
 need to either re\-link or \fBnpm rebuild \-g\fP to update compiled packages,
 of course\.)
 .P
-More info at \fBnpm\-link\fP \fI/docs/cli\-commands/npm\-link\fR\|\.
+More info at npm help \fBlink\fP\|\.
 .SS Before Publishing: Make Sure Your Package Installs and Works
 .P
 \fBThis is important\.\fR
@@ -249,7 +248,7 @@ npm adduser
 .P
 and then follow the prompts\.
 .P
-This is documented better in npm\-adduser \fI/docs/cli\-commands/npm\-adduser\fR\|\.
+This is documented better in npm help adduser\.
 .SS Publish your package
 .P
 This part's easy\.  In the root of your folder, do this:
@@ -277,15 +276,15 @@ Tell the world how easy it is to install your program!
 .IP \(bu 2
 npm help npm
 .IP \(bu 2
-npm help npm\-init
+npm help init
 .IP \(bu 2
-npm help package\-json
+npm help package\.json
 .IP \(bu 2
 npm help scripts
 .IP \(bu 2
-npm help npm\-publish
+npm help publish
 .IP \(bu 2
-npm help npm\-adduser
+npm help adduser
 .IP \(bu 2
 npm help registry
 
diff --git a/deps/npm/man/man7/disputes.7 b/deps/npm/man/man7/disputes.7
index 4e4e87df33..c815d20635 100644
--- a/deps/npm/man/man7/disputes.7
+++ b/deps/npm/man/man7/disputes.7
@@ -1,7 +1,6 @@
-.TH "DISPUTES" "" "November 2019" "" ""
+.TH "DISPUTES" "7" "November 2019" "" ""
 .SH "NAME"
-\fBdisputes\fR
-.SH Handling Module Name Disputes
+\fBdisputes\fR \- Handling Module Name Disputes
 .P
 This document describes the steps that you should take to resolve module name
 disputes with other npm publishers\. It also describes special steps you should
@@ -145,6 +144,6 @@ License\.
 .IP \(bu 2
 npm help registry
 .IP \(bu 2
-npm help npm\-owner
+npm help owner
 
 .RE
diff --git a/deps/npm/man/man7/orgs.7 b/deps/npm/man/man7/orgs.7
index 072979eb80..2c52a2db46 100644
--- a/deps/npm/man/man7/orgs.7
+++ b/deps/npm/man/man7/orgs.7
@@ -1,7 +1,6 @@
-.TH "ORGS" "" "November 2019" "" ""
+.TH "ORGS" "7" "November 2019" "" ""
 .SH "NAME"
-\fBorgs\fR
-.SH Working with Teams & Orgs
+\fBorgs\fR \- Working with Teams & Orgs
 .SS Description
 .P
 There are three levels of org users:
@@ -24,9 +23,9 @@ The developer will be able to access packages based on the teams they are on\. A
 There are two main commands:
 .RS 0
 .IP 1. 3
-\fBnpm team\fP see npm\-team \fI/docs/cli\-commands/npm\-team\fR for more details
+\fBnpm team\fP see npm help team for more details
 .IP 2. 3
-\fBnpm access\fP see npm\-access \fI/docs/cli\-commands/npm\-access\fR for more details
+\fBnpm access\fP see npm help access for more details
 
 .RE
 .SS Team Admins create teams
@@ -138,9 +137,9 @@ npm access ls\-collaborators <pkg>
 .SS See also
 .RS 0
 .IP \(bu 2
-npm help npm\-team
+npm help team
 .IP \(bu 2
-npm help npm\-access
+npm help access
 .IP \(bu 2
 npm help scope
 
diff --git a/deps/npm/man/man7/registry.7 b/deps/npm/man/man7/registry.7
index 11ba7b6b27..bbb5e802bf 100644
--- a/deps/npm/man/man7/registry.7
+++ b/deps/npm/man/man7/registry.7
@@ -1,7 +1,6 @@
-.TH "REGISTRY" "" "November 2019" "" ""
+.TH "REGISTRY" "7" "November 2019" "" ""
 .SH "NAME"
-\fBregistry\fR
-.SH The JavaScript Package Registry
+\fBregistry\fR \- The JavaScript Package Registry
 .SS Description
 .P
 To resolve packages by name and version, npm talks to a registry website
@@ -26,9 +25,9 @@ https://skimdb\.npmjs\.com/registry\|\.  The code for the couchapp is
 available at https://github\.com/npm/npm\-registry\-couchapp\|\.
 .P
 The registry URL used is determined by the scope of the package (see
-\fBnpm\-scope\fP \fIscope\fR\|\. If no scope is specified, the default registry is used, which is
-supplied by the \fBregistry\fP config parameter\.  See \fBnpm\-config\fP \fI/docs/cli\-commands/npm\-config\fR,
-\fBnpmrc\fP \fI/docs/configuring\-npm/npmrc\fR, and \fBnpm\-config\fP \fI/docs/using\-npm/config\fR for more on managing npm's configuration\.
+npm help \fBscope\fP\|\. If no scope is specified, the default registry is used, which is
+supplied by the \fBregistry\fP config parameter\.  See npm help \fBconfig\fP,
+npm help \fBnpmrc\fP, and npm help \fBconfig\fP for more on managing npm's configuration\.
 .SS Does npm send any information about me back to the registry?
 .P
 Yes\.
@@ -76,7 +75,7 @@ published at all, or
 \fB"publishConfig":{"registry":"http://my\-internal\-registry\.local"}\fP
 to force it to be published only to your internal registry\.
 .P
-See \fBpackage\.json\fP \fI/docs/configuring\-npm/package\-json\fR for more info on what goes in the package\.json file\.
+See npm help \fBpackage\.json\fP for more info on what goes in the package\.json file\.
 .SS Will you replicate from my registry into the public one?
 .P
 No\.  If you want things to be public, then publish them into the public
@@ -92,7 +91,7 @@ Yes, head over to https://www\.npmjs\.com/
 .SS See also
 .RS 0
 .IP \(bu 2
-npm help npm\-config
+npm help config
 .IP \(bu 2
 npm help config
 .IP \(bu 2
diff --git a/deps/npm/man/man7/removal.7 b/deps/npm/man/man7/removal.7
index 8c4e70c953..a4df8b4461 100644
--- a/deps/npm/man/man7/removal.7
+++ b/deps/npm/man/man7/removal.7
@@ -1,7 +1,6 @@
-.TH "REMOVAL" "" "November 2019" "" ""
+.TH "REMOVAL" "7" "November 2019" "" ""
 .SH "NAME"
-\fBremoval\fR
-.SH Cleaning the Slate
+\fBremoval\fR \- Cleaning the Slate
 .SS Synopsis
 .P
 So sad to see you go\.
@@ -69,10 +68,8 @@ find /usr/local/{lib/node,bin} \-exec grep \-l npm \\{\\} \\; ;
 .SS See also
 .RS 0
 .IP \(bu 2
-README
+npm help uninstall
 .IP \(bu 2
-npm help npm\-uninstall
-.IP \(bu 2
-npm help npm\-prune
+npm help prune
 
 .RE
diff --git a/deps/npm/man/man7/scope.7 b/deps/npm/man/man7/scope.7
index e1c8b3f9f1..ffe5570ae8 100644
--- a/deps/npm/man/man7/scope.7
+++ b/deps/npm/man/man7/scope.7
@@ -1,7 +1,6 @@
-.TH "SCOPE" "" "November 2019" "" ""
+.TH "SCOPE" "7" "November 2019" "" ""
 .SH "NAME"
-\fBscope\fR
-.SH Scoped packages
+\fBscope\fR \- Scoped packages
 .SS Description
 .P
 All npm packages have a name\. Some package names also have a scope\. A scope
@@ -55,7 +54,7 @@ Or in \fBpackage\.json\fP:
 .RE
 .P
 Note that if the \fB@\fP symbol is omitted, in either case, npm will instead attempt to
-install from GitHub; see \fBnpm\-install\fP \fI/docs/cli\-commands/npm\-install\fR\|\.
+install from GitHub; see npm help \fBinstall\fP\|\.
 .SS Requiring scoped packages
 .P
 Because scoped packages are installed into a scope folder, you have to
@@ -126,11 +125,11 @@ that registry instead\.
 .SS See also
 .RS 0
 .IP \(bu 2
-npm help npm\-install
+npm help install
 .IP \(bu 2
-npm help npm\-publish
+npm help publish
 .IP \(bu 2
-npm help npm\-access
+npm help access
 .IP \(bu 2
 npm help registry
 
diff --git a/deps/npm/man/man7/scripts.7 b/deps/npm/man/man7/scripts.7
index 7301652987..7517c59975 100644
--- a/deps/npm/man/man7/scripts.7
+++ b/deps/npm/man/man7/scripts.7
@@ -1,14 +1,13 @@
-.TH "SCRIPTS" "" "November 2019" "" ""
+.TH "SCRIPTS" "7" "November 2019" "" ""
 .SH "NAME"
-\fBscripts\fR
-.SH How npm handles the "scripts" field
+\fBscripts\fR \- How npm handles the "scripts" field
 .SS Description
 .P
 npm supports the "scripts" property of the package\.json file, for the
 following scripts:
 .RS 0
 .IP \(bu 2
-\fBprepublish\fR:
+\fBprepublish\fR (\fIas of npm@5, \fBprepublish\fP is deprecated\. Use \fBprepare\fP for build steps and \fBprepublishOnly\fP for upload\-only\.\fR):
 Run BEFORE the package is packed and published, as well as on local \fBnpm
 install\fP without any arguments\. (See below)
 .IP \(bu 2
@@ -73,7 +72,7 @@ Run by the \fBnpm shrinkwrap\fP command\.
 Additionally, arbitrary scripts can be executed by running \fBnpm
 run\-script <stage>\fP\|\. \fIPre\fR and \fIpost\fR commands with matching
 names will be run for those as well (e\.g\. \fBpremyscript\fP, \fBmyscript\fP,
-\fBpostmyscript\fP)\. Scripts from dependencies can be run with
+\fBpostmyscript\fP)\. Scripts from dependencies can be run with 
 \fBnpm explore <pkg> \-\- npm run <stage>\fP\|\.
 .SS Prepublish and Prepare
 .SS Deprecation Note
@@ -170,8 +169,8 @@ The package\.json fields are tacked onto the \fBnpm_package_\fP prefix\. So,
 for instance, if you had \fB{"name":"foo", "version":"1\.2\.5"}\fP in your
 package\.json file, then your package scripts would have the
 \fBnpm_package_name\fP environment variable set to "foo", and the
-\fBnpm_package_version\fP set to "1\.2\.5"\.  You can access these variables
-in your code with \fBprocess\.env\.npm_package_name\fP and
+\fBnpm_package_version\fP set to "1\.2\.5"\.  You can access these variables 
+in your code with \fBprocess\.env\.npm_package_name\fP and 
 \fBprocess\.env\.npm_package_version\fP, and so on for other fields\.
 .SS configuration
 .P
@@ -290,7 +289,7 @@ only will prevent some optional features, then it's better to just
 print a warning and exit successfully\.
 .IP \(bu 2
 Try not to use scripts to do what npm can do for you\.  Read through
-\fBpackage\.json\fP \fI/docs/configuring\-npm/package\-json\fR to see all the things that you can specify and enable
+npm help \fBpackage\.json\fP to see all the things that you can specify and enable
 by simply describing your package appropriately\.  In general, this
 will lead to a more robust and consistent state\.
 .IP \(bu 2
@@ -313,12 +312,12 @@ scripts is for compilation which must be done on the target architecture\.
 .SS See Also
 .RS 0
 .IP \(bu 2
-npm help npm\-run\-script
+npm help run\-script
 .IP \(bu 2
-npm help package\-json
+npm help package\.json
 .IP \(bu 2
 npm help developers
 .IP \(bu 2
-npm help npm\-install
+npm help install
 
 .RE
diff --git a/deps/npm/man/man7/semver.7 b/deps/npm/man/man7/semver.7
index 0db8cda6e1..b65c475f6e 100644
--- a/deps/npm/man/man7/semver.7
+++ b/deps/npm/man/man7/semver.7
@@ -1,6 +1,6 @@
-.TH "NPM" "" "November 2019" "" ""
+.TH "SEMVER" "7" "November 2019" "" ""
 .SH "NAME"
-\fBnpm\fR
+\fBsemver\fR \- The semantic versioner for npm
 .SH Install
 .P
 .RS 2
author	claudiahdz <cghr1990@gmail.com>	2019-11-18 21:01:39 +0200
committer	Myles Borins <mylesborins@google.com>	2019-11-20 19:16:47 -0500
commit	a7c7c703aff362f06ef5d49451a0f79fd289910f (patch)
tree	48f9d01b32d55d420f229c4889a5a61178419223 /deps/npm/man
parent	a30a9f8193ddd61dfadc2d5d79784b682027b319 (diff)
download	node-new-a7c7c703aff362f06ef5d49451a0f79fd289910f.tar.gz