deps: upgrade npm to 2.8.3

7 files changed, 68 insertions, 11 deletions

diff --git a/deps/npm/man/man1/npm-dist-tag.1 b/deps/npm/man/man1/npm-dist-tag.1
index 31d6e96438..568b6aeccd 100644
--- a/deps/npm/man/man1/npm-dist-tag.1
+++ b/deps/npm/man/man1/npm-dist-tag.1
@@ -47,7 +47,8 @@ npm install \-\-tag <tag>
 .P
 This also applies to \fBnpm dedupe\fR\|\.
 .P
-Publishing a package always sets the "latest" tag to the published version\.
+Publishing a package sets the "latest" tag to the published version unless the
+\fB\-\-tag\fR option is used\. For example, \fBnpm publish \-\-tag=beta\fR\|\.
 .SH PURPOSE
 .P
 Tags can be used to provide an alias instead of version numbers\.  For
diff --git a/deps/npm/man/man1/npm-install.1 b/deps/npm/man/man1/npm-install.1
index d7b2c00c88..c27de4cadc 100644
--- a/deps/npm/man/man1/npm-install.1
+++ b/deps/npm/man/man1/npm-install.1
@@ -191,8 +191,52 @@ fetch the package by name if it is not valid\.
     npm install mygithubuser/myproject
 .fi
 .RE
- To reference a package in a git repo that is not on GitHub, see git
- remote urls below\.
+ To reference a package in a generic git repo (not on GitHub), see git remote
+ urls below\.
+.IP \(bu 2
+\fBnpm install github:<githubname>/<githubrepo>\fR:
+  The same as the above, but explicitly marked as a GitHub dependency\.
+  Example:
+.P
+.RS 2
+.nf
+    npm install github:npm/npm
+.fi
+.RE
+.IP \(bu 2
+\fBnpm install gist:[<githubname>/]<gistID>\fR:
+  Install the package at \fBhttps://gist\.github\.com/gistID\fR by attempting to
+  clone it using \fBgit\fR\|\. The GitHub username associated with the gist is
+  optional and will not be saved in \fBpackage\.json\fR if \fB\-\-save\fR is used\.
+  Example:
+.P
+.RS 2
+.nf
+    npm install gist:101a11beef
+.fi
+.RE
+.IP \(bu 2
+\fBnpm install bitbucket:<bitbucketname>/<bitbucketrepo>\fR:
+  Install the package at \fBhttps://bitbucket\.org/bitbucketname/bitbucketrepo\fR
+  by attempting to clone it using \fBgit\fR\|\.
+  Example:
+.P
+.RS 2
+.nf
+    npm install bitbucket:mybitbucketuser/myproject
+.fi
+.RE
+.IP \(bu 2
+\fBnpm install gitlab:<gitlabname>/<gitlabrepo>\fR:
+  Install the package at \fBhttps://gitlab\.com/gitlabname/gitlabrepo\fR
+  by attempting to clone it using \fBgit\fR\|\.
+  Example:
+.P
+.RS 2
+.nf
+    npm install gitlab:mygitlabuser/myproject
+.fi
+.RE
 .IP \(bu 2
 \fBnpm install <git remote url>\fR:
   Install a package by cloning a git remote url\.  The format of the git
@@ -200,7 +244,7 @@ fetch the package by name if it is not valid\.
 .P
 .RS 2
 .nf
-    <protocol>://[<user>@]<hostname><separator><path>[#<commit\-ish>]
+    <protocol>://[<user>[:<password>]@]<hostname><separator><path>[#<commit\-ish>]
 .fi
 .RE
   \fB<protocol>\fR is one of \fBgit\fR, \fBgit+ssh\fR, \fBgit+http\fR, or
diff --git a/deps/npm/man/man1/npm-ls.1 b/deps/npm/man/man1/npm-ls.1
index b647bfd372..35c5ae46d9 100644
--- a/deps/npm/man/man1/npm-ls.1
+++ b/deps/npm/man/man1/npm-ls.1
@@ -23,7 +23,7 @@ For example, running \fBnpm ls promzard\fR in npm's source tree will show:
 .P
 .RS 2
 .nf
-npm@2.7.6 /path/to/npm
+npm@2.8.3 /path/to/npm
 └─┬ init\-package\-json@0\.0\.4
   └── promzard@0\.1\.5
 .fi
diff --git a/deps/npm/man/man1/npm.1 b/deps/npm/man/man1/npm.1
index c9aca06067..e11973239e 100644
--- a/deps/npm/man/man1/npm.1
+++ b/deps/npm/man/man1/npm.1
@@ -10,7 +10,7 @@ npm <command> [args]
 .RE
 .SH VERSION
 .P
-2.7.6
+2.8.3
 .SH DESCRIPTION
 .P
 npm is the package manager for the Node JavaScript platform\.  It puts
diff --git a/deps/npm/man/man3/npm.3 b/deps/npm/man/man3/npm.3
index af4c999080..22751011eb 100644
--- a/deps/npm/man/man3/npm.3
+++ b/deps/npm/man/man3/npm.3
@@ -20,7 +20,7 @@ npm\.load([configObject, ]function (er, npm) {
 .RE
 .SH VERSION
 .P
-2.7.6
+2.8.3
 .SH DESCRIPTION
 .P
 This is the API documentation for npm\.
diff --git a/deps/npm/man/man5/npm-json.5 b/deps/npm/man/man5/npm-json.5
index 62fce52d8d..088e62bdc3 100644
--- a/deps/npm/man/man5/npm-json.5
+++ b/deps/npm/man/man5/npm-json.5
@@ -302,12 +302,18 @@ The URL should be a publicly available (perhaps read\-only) url that can be hand
 directly to a VCS program without any modification\.  It should not be a url to an
 html project page that you put in your browser\.  It's for computers\.
 .P
-For GitHub repositories you can use the same shortcut syntax you use for \fBnpm
-install\fR:
+For GitHub, GitHub gist, Bitbucket, or GitLab repositories you can use the same
+shortcut syntax you use for \fBnpm install\fR:
 .P
 .RS 2
 .nf
 "repository": "npm/npm"
+
+"repository": "gist:11081aaa281"
+
+"repository": "bitbucket:example/repo"
+
+"repository": "gitlab:another/repo"
 .fi
 .RE
 .SH scripts
diff --git a/deps/npm/man/man5/package.json.5 b/deps/npm/man/man5/package.json.5
index 62fce52d8d..088e62bdc3 100644
--- a/deps/npm/man/man5/package.json.5
+++ b/deps/npm/man/man5/package.json.5
@@ -302,12 +302,18 @@ The URL should be a publicly available (perhaps read\-only) url that can be hand
 directly to a VCS program without any modification\.  It should not be a url to an
 html project page that you put in your browser\.  It's for computers\.
 .P
-For GitHub repositories you can use the same shortcut syntax you use for \fBnpm
-install\fR:
+For GitHub, GitHub gist, Bitbucket, or GitLab repositories you can use the same
+shortcut syntax you use for \fBnpm install\fR:
 .P
 .RS 2
 .nf
 "repository": "npm/npm"
+
+"repository": "gist:11081aaa281"
+
+"repository": "bitbucket:example/repo"
+
+"repository": "gitlab:another/repo"
 .fi
 .RE
 .SH scripts