deps: upgrade npm to 2.8.4

Reviewed-By: Julien Gilli <julien.gilli@joyent.com>
PR-URL: #20311

Author: othiym23

deps/npm/.mailmap

@@ -1,16 +1,16 @@
-Arlo Breault <arlolra@gmail.com>
 Alex K. Wolfe <alexkwolfe@gmail.com>
 Andrew Bradley <cspotcode@gmail.com>
 Andrew Lunny <alunny@gmail.com>
+Arlo Breault <arlolra@gmail.com>
 Benjamin Coe <bencoe@gmail.com>
 Brian White <mscdex@mscdex.net> <mscdex@gmail.com>
 Charlie Robbins <charlie.robbins@gmail.com>
 Dalmais Maxence <root@ip-10-195-202-5.ec2.internal>
 David Beitey <david@davidjb.com>
 Domenic Denicola <domenic@domenicdenicola.com>
 Einar Otto Stangvik <einaros@gmail.com>
-Evan Lucas <evan@btc.com> <evanlucas@me.com>
 Evan Lucas <evan@btc.com> <evan.lucas@hattiesburgclinic.com>
+Evan Lucas <evan@btc.com> <evanlucas@me.com>
 Faiq Raza <faiqrazarizvi@gmail.com>
 Forbes Lindesay <forbes@lindesay.co.uk>
 Forrest L Norvell <ogd@aoaioxxysz.net> <forrest@npmjs.com>
@@ -22,16 +22,20 @@ Jake Verbaten <raynos2@gmail.com>
 James Sanders <jimmyjazz14@gmail.com>
 Jason Smith <jhs@iriscouch.com>
 Jonas Weber <github@jonasw.de>
+Julien Meddah <julien.meddah@deveryware.com>
 Kris Windham <kriswindham@gmail.com>
 Lin Clark <lin.w.clark@gmail.com>
 Maciej Małecki <me@mmalecki.com> <maciej.malecki@notimplemented.org>
-Maximilian Antoni <mail@maxantoni.de> <maximilian.antoni@juliusbaer.com>
-Maxim Bogushevich <boga1@mail.ru>
 Max Goodman <c@chromakode.com>
+Maxim Bogushevich <boga1@mail.ru>
+Maximilian Antoni <mail@maxantoni.de> <maximilian.antoni@juliusbaer.com>
 Nicolas Morel <marsup@gmail.com>
 Olivier Melcher <olivier.melcher@gmail.com>
+Ra'Shaun Stovall <rashaunstovall@gmail.com>
+Rebecca Turner <me@re-becca.org> <turner@mikomi.org>
 Ryan Emery <seebees@gmail.com>
 Sam Mikes <smikes@cubane.com>
+Takaya Kobayashi <jigsaw@live.jp>
 Tony <zearin@gonk.net>
 Visnu Pitiyanuvath <visnupx@gmail.com>
 Will Elwood <w.elwood08@gmail.com>

deps/npm/.travis.yml

@@ -8,7 +8,7 @@ env:
   - DEPLOY_VERSION=testing
 before_install:
   - "npm config set spin false"
-  - "npm install -g npm@~2"
+  - "npm install -g npm/npm"
   - "sudo mkdir -p /var/run/couchdb"
 script: "npm run-script test-all"
 notifications:

deps/npm/AUTHORS

@@ -201,7 +201,7 @@ Chulki Lee <chulki.lee@gmail.com>
 dead_horse <dead_horse@qq.com>
 Kenan Yildirim <kenan@kenany.me>
 Laurie Voss <git@seldo.com>
-Rebecca Turner <turner@mikomi.org>
+Rebecca Turner <me@re-becca.org>
 Hunter Loftis <hunter@hunterloftis.com>
 Peter Richardson <github@zoomy.net>
 Jussi Kalliokoski <jussi.kalliokoski@gmail.com>
@@ -264,3 +264,10 @@ Oli Evans <oli@zilla.org.uk>
 Matt Brennan <mattyb1000@gmail.com>
 Jeff Barczewski <jeff.barczewski@gmail.com>
 Danny Fritz <dannyfritz@gmail.com>
+Takaya Kobayashi <jigsaw@live.jp>
+Ra'Shaun Stovall <rashaunstovall@gmail.com>
+Julien Meddah <julien.meddah@deveryware.com>
+Michiel Sikma <michiel@wedemandhtml.com>
+Jakob Krigovsky <jakob.krigovsky@gmail.com>
+Charmander <~@charmander.me>
+erik wienhold <git@ewie.name>

deps/npm/CHANGELOG.md

@@ -40,7 +40,7 @@ There's a pretty robust install script at
 
 Here's an example using curl:
 
-    curl -L https://npmjs.com/install.sh | sh
+    curl -L https://www.npmjs.com/install.sh | sh
 
 ### Slightly Fancier
 
@@ -64,11 +64,11 @@ for testing, or running stuff without actually installing npm itself.)
 
 ## Windows Install or Upgrade
 
-You can download a zip file from <https://github.com/npm/npm/releases>, and unpack it
-in the same folder where node.exe lives.
+You can download a zip file from <https://github.com/npm/npm/releases>, and
+unpack it in the `node_modules\npm\` folder inside node's installation folder.
 
-The latest version in a zip file is 1.4.12.  To upgrade to npm 2, follow the
-Windows upgrade instructions in the npm Troubleshooting Guide:
+To upgrade to npm 2, follow the Windows upgrade instructions in
+the npm Troubleshooting Guide:
 
 <https://github.com/npm/npm/wiki/Troubleshooting#upgrading-on-windows>
 

deps/npm/README.md

@@ -1,5 +1,5 @@
-if not defined npm_config_node_gyp (
-  node "%~dp0\..\..\node_modules\node-gyp\bin\node-gyp.js" %*
-) else (
-  %npm_config_node_gyp% %*
-)
+if not defined npm_config_node_gyp (
+  node "%~dp0\..\..\node_modules\node-gyp\bin\node-gyp.js" %*
+) else (
+  %npm_config_node_gyp% %*
+)

deps/npm/bin/node-gyp-bin/node-gyp.cmd

@@ -33,7 +33,8 @@ When installing dependencies, a preferred tagged version may be specified:
 
 This also applies to `npm dedupe`.
 
-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
+`--tag` option is used. For example, `npm publish --tag=beta`.
 
 ## PURPOSE
 

deps/npm/doc/cli/npm-dist-tag.md

@@ -164,15 +164,51 @@ after packing it up into a tarball (b).
 
           npm install mygithubuser/myproject
 
-   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.
+
+* `npm install github:<githubname>/<githubrepo>`:
+
+    The same as the above, but explicitly marked as a GitHub dependency.
+
+    Example:
+
+          npm install github:npm/npm
+
+* `npm install gist:[<githubname>/]<gistID>`:
+
+    Install the package at `https://gist.github.com/gistID` by attempting to
+    clone it using `git`. The GitHub username associated with the gist is
+    optional and will not be saved in `package.json` if `--save` is used.
+
+    Example:
+
+          npm install gist:101a11beef
+
+* `npm install bitbucket:<bitbucketname>/<bitbucketrepo>`:
+
+    Install the package at `https://bitbucket.org/bitbucketname/bitbucketrepo`
+    by attempting to clone it using `git`.
+
+    Example:
+
+          npm install bitbucket:mybitbucketuser/myproject
+
+* `npm install gitlab:<gitlabname>/<gitlabrepo>`:
+
+    Install the package at `https://gitlab.com/gitlabname/gitlabrepo`
+    by attempting to clone it using `git`.
+
+    Example:
+
+          npm install gitlab:mygitlabuser/myproject
 
 * `npm install <git remote url>`:
 
     Install a package by cloning a git remote url.  The format of the git
     url is:
 
-          <protocol>://[<user>@]<hostname><separator><path>[#<commit-ish>]
+          <protocol>://[<user>[:<password>]@]<hostname><separator><path>[#<commit-ish>]
 
     `<protocol>` is one of `git`, `git+ssh`, `git+http`, or
     `git+https`.  If no `<commit-ish>` is specified, then `master` is

deps/npm/doc/cli/npm-install.md

@@ -39,7 +39,7 @@ For example:
 
 Now, any changes to ~/projects/node-redis will be reflected in
 ~/projects/node-bloggy/node_modules/node-redis/. Note that the link should
-be to the package name, not the directory name for that package.
+be to the package name, not the directory name for that package. 
 
 You may also shortcut the two steps in one.  For example, to do the
 above use-case in a shorter way:

deps/npm/doc/cli/npm-link.md

@@ -114,7 +114,7 @@ is an object with a "name" field and optionally "url" and "email", like this:
 
 Or you can shorten that all into a single string, and npm will parse it for you:
 
-    "Barney Rubble <b@rubble.com> (http://barnyrubble.tumblr.com/)
+    "Barney Rubble <b@rubble.com> (http://barnyrubble.tumblr.com/)"
 
 Both email and url are optional either way.
 
@@ -272,11 +272,17 @@ The URL should be a publicly available (perhaps read-only) url that can be hande
 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.
 
-For GitHub repositories you can use the same shortcut syntax you use for `npm
-install`:
+For GitHub, GitHub gist, Bitbucket, or GitLab repositories you can use the same
+shortcut syntax you use for `npm install`:
 
     "repository": "npm/npm"
 
+    "repository": "gist:11081aaa281"
+
+    "repository": "bitbucket:example/repo"
+
+    "repository": "gitlab:another/repo"
+
 ## scripts
 
 The "scripts" property is a dictionary containing script commands that are run