deps: upgrade npm to 4.2.0

PR-URL: #11389 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
MylesBorins · Mar 29, 2017 · Mar 23, 2017 · Mar 17, 2017 · Sep 21, 2015 · Mar 20, 2017
commit 2767e2d3cc6e270095101ce6d7e7473d9e19bd7a
diff --git a/deps/npm/.mailmap b/deps/npm/.mailmap
@@ -21,7 +21,7 @@ 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>
+Forrest L Norvell <ogd@aoaioxxysz.net> <forrest@npmjs.com> <othiym23@gmail.com>
 Gabriel Barros <descartavel1@gmail.com>
 Geoff Flarity <geoff.flarity@gmail.com> <gflarity@raptvm-x02.(none)>
 Gregers Gram Rygg <gregers.gram.rygg@finn.no>

diff --git a/deps/npm/AUTHORS b/deps/npm/AUTHORS
@@ -446,3 +446,7 @@ Ville Lahdenvuo <tuhoojabotti@gmail.com>
 Natalie Wolfe <nwolfe@newrelic.com>
 Andrew Schmadel <aschmadel@learningobjects.com>
 Jonah Moses <jonahkmoses@gmail.com>
+Daijirō Wachi <daijiro.wachi@gmail.com>
+Dmitry Litvinchenko <karaliti@gmail.com>
+chocolateboy <chocolate@cpan.org>
+Henry Zhu <hi@henryzoo.com>
diff --git a/deps/npm/CHANGELOG.md b/deps/npm/CHANGELOG.md
@@ -1,3 +1,117 @@
+### v4.2.0 (2017-01-26):
+
+Hi all! I'm Kat, and I'm currently sitting in a train traveling at ~300km/h
+through Spain. So clearly, this release should have *something* to do with
+speed. And it does! Heck, with this release, you could say we're really
+_blazing_, even. 🌲🔥😏
+
+#### IMPROVED CLI SEARCH~
+
+You might recall if you've been keeping up that one of the reasons for a
+semver-major bump to `npm@4` was an improved CLI search (read: no longer blowing
+up Node). The work done for that new search system, while still relying on a
+full metadata download and local search, was also meant to act as groundwork for
+then-ongoing work on a brand-new, smarter search system for npm. Shortly after
+`npm@4` came out, the bulk of the server-side work was done, and with this
+release, the npm CLI has integrated use of the new endpoint for high-quality,
+fast-turnaround searches.
+
+No, seriously, it's *fast*. And *relevant*:
+
+[![GOTTA GO FAST! This is a gif of the new npm search returning results in around a second for `npm search web framework`.](https://cloud.githubusercontent.com/assets/17535/21954136/f007e8be-d9fd-11e6-9231-f899c12790e0.gif)](https://github.com/npm/npm/pull/15481)
+
+Give it a shot! And remember to check out the new website version of the search,
+too, which uses the same backend as the CLI now. 🎉
+
+Incidentally, the backend is a public service, so you can write your own search
+tools, be they web-based, CLI, or GUI-based. You can read up on the [full
+documentation for the search
+endpoint](https://github.com/npm/registry/blob/master/docs/REGISTRY-API.md#get-v1search),
+and let us know about the cool things you come up with!
+
+* [`ce3ca51`](https://github.com/npm/npm/commit/ce3ca51ca2d60e15e901c8bf6256338e53e1eca2)
+  [#15481](https://github.com/npm/npm/pull/15481)
+  Add an internal `gunzip-maybe` utility for optional gunzipping.
+  ([@zkat](https://github.com/zkat))
+* [`e322932`](https://github.com/npm/npm/commit/e3229324d507fda10ea9e94fd4de8a4ae5025c75) [`a53055e`](https://github.com/npm/npm/commit/a53055e423f1fe168f05047aa0dfec6d963cb211) [`a1f4365`](https://github.com/npm/npm/commit/a1f436570730c6e4a173ca92d1967a87c29b7f2d) [`c56618c`](https://github.com/npm/npm/commit/c56618c62854ea61f6f716dffe7bcac80b5f4144)
+  [#15481](https://github.com/npm/npm/pull/15481)
+  Add support for using the new npm search endpoint for fast, quality search
+  results. Includes a fallback to "classic" search.
+  ([@zkat](https://github.com/zkat))
+
+#### WHERE DID THE DEBUG LOGS GO
+
+This is another pretty significant change: Usually, when the npm process
+crashed, you would get an `npm-debug.log` in your current working directory.
+This debug log would get cleared out as soon as you ran npm again. This was a
+bit annoying because 1) you would get a random file in your `git status` that
+you might accidentally commit, and 2) if you hit a hard-to-reproduce bug and
+instinctually tried again, you would no longer have access to the repro
+`npm-debug.log`.
+
+So now, any time a crash happens, we'll save your debug logs to your cache
+folder, under `_logs` (`~/.npm` on *nix, by default -- use `npm config get
+cache` to see what your current value is). The cache will now hold a
+(configurable) number of `npm-debug.log` files, which you can access in the
+future. Hopefully this will help clean stuff up and reduce frustration from
+missed repros! In the future, this will also be used by `npm report` to make it
+super easy to put up issues about crashes you run into with npm. 💃🕺🏿👯‍♂️
+
+* [`04fca22`](https://github.com/npm/npm/commit/04fca223a0f704b69340c5f81b26907238fad878)
+  [#11439](https://github.com/npm/npm/pull/11439)
+  Put debug logs in `$(npm get cache)/_logs` and store multiple log files.
+  ([@KenanY](https://github.com/KenanY))
+  ([@othiym23](https://github.com/othiym23))
+  ([@isaacs](https://github.com/isaacs))
+  ([@iarna](https://github.com/iarna))
+
+#### DOCS
+
+* [`ae8e71c`](https://github.com/npm/npm/commit/ae8e71c2b7d64d782af287a21e146d7cea6e5273)
+  [#15402](https://github.com/npm/npm/pull/15402)
+  Add missing backtick in one of the `npm doctor` messages.
+  ([@watilde](https://github.com/watilde), [@charlotteis](https://github.com/charlotteis))
+* [`821fee6`](https://github.com/npm/npm/commit/821fee6d0b12a324e035c397ae73904db97d07d2)
+  [#15480](https://github.com/npm/npm/pull/15480)
+  Clarify that unscoped packages can depend on scoped packages and vice-versa.
+  ([@chocolateboy](https://github.com/chocolateboy))
+* [`2ee45a8`](https://github.com/npm/npm/commit/2ee45a884137ae0706b7c741c671fef2cb3bac96)
+  [#15515](https://github.com/npm/npm/pull/15515)
+  Update minimum supported Node version number in the README to `node@>=4`.
+  ([@watilde](https://github.com/watilde))
+* [`af06aa9`](https://github.com/npm/npm/commit/af06aa9a357578a8fd58c575f3dbe55bc65fc376)
+  [#15520](https://github.com/npm/npm/pull/15520)
+  Add section to `npm-scope` docs to explain that scope owners will own scoped
+  packages with that scope. That is, user `@alice` is not allowed to publish to
+  `@bob/my-package` unless explicitly made an owner by user (or org) `@bob`.
+  ([@hzoo](https://github.com/hzoo))
+* [`bc892e6`](https://github.com/npm/npm/commit/bc892e6d07a4c6646480703641a4d71129c38b6d)
+  [#15539](https://github.com/npm/npm/pull/15539)
+  Replace `http` with `https` and fix typos in some docs.
+  ([@watilde](https://github.com/watilde))
+* [`1dfe875`](https://github.com/npm/npm/commit/1dfe875b9ac61a0ab9f61a2eab02bacf6cce583c)
+  [#15545](https://github.com/npm/npm/pull/15545)
+  Update Node.js download link to point to the right place.
+  ([@watilde](https://github.com/watilde))
+
+#### DEPENDENCIES
+
+  * [`b824bfb`](https://github.com/npm/npm/commit/b824bfbeb2d89c92762e9170b026af98b5a3668a)
+    `ansi-regex@2.1.1`
+  * [`81ea3e8`](https://github.com/npm/npm/commit/81ea3e8e4ea34cd9c2b418512dcb508abcee1380)
+    `mississippi@1.3.0`
+
+#### MISC
+
+* [`98df212`](https://github.com/npm/npm/commit/98df212a91fd6ff4a02b9cd247f4166f93d3977a)
+  [#15492](https://github.com/npm/npm/pull/15492)
+  Update the "master" node version used for AppVeyor to `node@7`.
+  ([@watilde](https://github.com/watilde))
+* [`d75fc03`](https://github.com/npm/npm/commit/d75fc03eda5364f12ac266fa4f66e31c2e44e864)
+  [#15413](https://github.com/npm/npm/pull/15413)
+  `npm run-script` now exits with the child process' exit code on exit.
+  ([@kapals](https://github.com/kapals))
+
 ### v4.1.2 (2017-01-12)
 
 We have a twee little release this week as we come back from the holidays.

diff --git a/deps/npm/README.md b/deps/npm/README.md
@@ -9,9 +9,9 @@ Much more info available via `npm help` once it's installed.
 
 ## IMPORTANT
 
-**You need node v0.10 or higher to run this program.**
+**You need node v4 or higher to run this program.**
 
-To install an old **and unsupported** version of npm that works on node 0.3
+To install an old **and unsupported** version of npm that works on node v0.12
 and prior, clone the git repo and dig through the old tags and branches.
 
 **npm is configured to use npm, Inc.'s public package registry at
@@ -84,7 +84,7 @@ for testing, or running stuff without actually installing npm itself.)
 Many improvements for Windows users have been made in npm 3 - you will have a better
 experience if you run a recent version of npm. To upgrade, either use [Microsoft's
 upgrade tool](https://github.com/felixrieseberg/npm-windows-upgrade),
-[download a new version of Node](http://nodejs.org/download/),
+[download a new version of Node](https://nodejs.org/en/download/),
 or follow the Windows upgrade instructions in the
 [npm Troubleshooting Guide](https://github.com/npm/npm/wiki/Troubleshooting#upgrading-on-windows).
 

diff --git a/deps/npm/appveyor.yml b/deps/npm/appveyor.yml
@@ -5,7 +5,7 @@ environment:
     # previous LTS is next most important
     - nodejs_version: "4"
     # then master
-    - nodejs_version: "5"
+    - nodejs_version: "7"
   COVERALLS_REPO_TOKEN:
     secure: XdC0aySefK0HLh1GNk6aKrzZPbCfPQLyA4mYtFGEp4DrTuZA/iuCUS0LDqFYO8JQ
 platform:

diff --git a/deps/npm/doc/files/package.json.md b/deps/npm/doc/files/package.json.md
@@ -119,18 +119,18 @@ array of license objects:
     // Not valid metadata
     { "license" :
       { "type" : "ISC"
-      , "url" : "http://opensource.org/licenses/ISC"
+      , "url" : "https://opensource.org/licenses/ISC"
       }
     }
 
     // Not valid metadata
     { "licenses" :
       [
         { "type": "MIT"
-        , "url": "http://www.opensource.org/licenses/mit-license.php"
+        , "url": "https://www.opensource.org/licenses/mit-license.php"
         }
       , { "type": "Apache-2.0"
-        , "url": "http://opensource.org/licenses/apache2.0.php"
+        , "url": "https://opensource.org/licenses/apache2.0.php"
         }
       ]
     }

diff --git a/deps/npm/doc/misc/npm-config.md b/deps/npm/doc/misc/npm-config.md
@@ -576,6 +576,13 @@ stderr.
 If the `color` config is set to true, then this stream will receive
 colored output if it is a TTY.
 
+### logs-max
+
+* Default: 10
+* Type: Number
+
+The maximum number of log files to store.
+
 ### long
 
 * Default: false
@@ -844,12 +851,21 @@ Space-separated options that limit the results from search.
 
 Space-separated options that are always passed to search.
 
+### searchlimit
+
+* Default: 20
+* Type: Number
+
+Number of items to limit search results to. Will not apply at all to legacy
+searches.
+
 ### searchstaleness
 
 * Default: 900 (15 minutes)
 * Type: Number
 
-The age of the cache, in seconds, before another registry request is made.
+The age of the cache, in seconds, before another registry request is made if
+using legacy search endpoint.
 
 ### send-metrics
 

diff --git a/deps/npm/doc/misc/npm-scope.md b/deps/npm/doc/misc/npm-scope.md
@@ -4,30 +4,35 @@ npm-scope(7) -- Scoped packages
 ## DESCRIPTION
 
 All npm packages have a name. Some package names also have a scope. A scope
-follows the usual rules for package names (url-safe characters, no leading dots
-or underscores). When used in package names, preceded by an @-symbol and
-followed by a slash, e.g.
+follows the usual rules for package names (URL-safe characters, no leading dots
+or underscores). When used in package names, scopes are preceded by an `@` symbol
+and followed by a slash, e.g.
 
     @somescope/somepackagename
 
 Scopes are a way of grouping related packages together, and also affect a few
 things about the way npm treats the package.
 
+Each npm user/organization has their own scope, and only you can add packages
+in your scope. This means you don't have to worry about someone taking your
+package name ahead of you. Thus it is also a good way to signal official packages
+for organizations.
+
 Scoped packages can be published and installed as of `npm@2` and are supported
-by the primary npm registry. The npm client is backwards-compatible with
-un-scoped registries, so it can be used to work with scoped and un-scoped
-registries at the same time.
+by the primary npm registry. Unscoped packages can depend on scoped packages and
+vice versa. The npm client is backwards-compatible with unscoped registries,
+so it can be used to work with scoped and unscoped registries at the same time.
 
 ## Installing scoped packages
 
 Scoped packages are installed to a sub-folder of the regular installation
 folder, e.g. if your other packages are installed in `node_modules/packagename`,
-scoped modules will be in `node_modules/@myorg/packagename`. The scope folder
-(`@myorg`) is simply the name of the scope preceded by an @-symbol, and can
+scoped modules will be installed in `node_modules/@myorg/packagename`. The scope
+folder (`@myorg`) is simply the name of the scope preceded by an `@` symbol, and can
 contain any number of scoped packages.
 
 A scoped package is installed by referencing it by name, preceded by an
-@-symbol, in `npm install`:
+`@` symbol, in `npm install`:
 
     npm install @myorg/mypackage
 
@@ -37,7 +42,7 @@ Or in `package.json`:
       "@myorg/mypackage": "^1.3.0"
     }
 
-Note that if the @-symbol is omitted in either case npm will instead attempt to
+Note that if the `@` symbol is omitted, in either case, npm will instead attempt to
 install from GitHub; see `npm-install(1)`.
 
 ## Requiring scoped packages
@@ -47,8 +52,8 @@ include the name of the scope when requiring them in your code, e.g.
 
     require('@myorg/mypackage')
 
-There is nothing special about the way Node treats scope folders, this is
-just specifying to require the module `mypackage` in the folder called `@myorg`.
+There is nothing special about the way Node treats scope folders. This
+simply requires the `mypackage` module in the folder named `@myorg`.
 
 ## Publishing scoped packages
 
@@ -57,14 +62,14 @@ published to any registry that supports them, including the primary npm
 registry.
 
 (As of 2015-04-19, and with npm 2.0 or better, the primary npm registry
-**does** support scoped packages)
+**does** support scoped packages.)
 
 If you wish, you may associate a scope with a registry; see below.
 
 ### Publishing public scoped packages to the primary npm registry
 
 To publish a public scoped package, you must specify `--access public` with
-the initial publication.  This will publish the package and set access
+the initial publication. This will publish the package and set access
 to `public` as if you had run `npm access public` after publishing.
 
 ### Publishing private scoped packages to the npm registry
@@ -75,7 +80,7 @@ account.
 
 You can then publish the module with `npm publish` or `npm publish
 --access restricted`, and it will be present in the npm registry, with
-restricted access.  You can then change the access permissions, if
+restricted access. You can then change the access permissions, if
 desired, with `npm access` or on the npmjs.com website.
 
 ## Associating a scope with a registry
@@ -105,3 +110,4 @@ that registry instead.
 * npm-install(1)
 * npm-publish(1)
 * npm-access(1)
+* npm-registry(7)
diff --git a/deps/npm/html/doc/README.html b/deps/npm/html/doc/README.html
@@ -15,8 +15,8 @@ <h2 id="synopsis">SYNOPSIS</h2>
 <p>This is just enough info to get you up and running.</p>
 <p>Much more info available via <code>npm help</code> once it&#39;s installed.</p>
 <h2 id="important">IMPORTANT</h2>
-<p><strong>You need node v0.10 or higher to run this program.</strong></p>
-<p>To install an old <strong>and unsupported</strong> version of npm that works on node 0.3
+<p><strong>You need node v4 or higher to run this program.</strong></p>
+<p>To install an old <strong>and unsupported</strong> version of npm that works on node v0.12
 and prior, clone the git repo and dig through the old tags and branches.</p>
 <p><strong>npm is configured to use npm, Inc.&#39;s public package registry at
 <a href="https://registry.npmjs.org">https://registry.npmjs.org</a> by default.</strong></p>
@@ -60,7 +60,7 @@ <h2 id="windows-install-or-upgrade">Windows Install or Upgrade</h2>
 <p>Many improvements for Windows users have been made in npm 3 - you will have a better
 experience if you run a recent version of npm. To upgrade, either use <a href="https://github.com/felixrieseberg/npm-windows-upgrade">Microsoft&#39;s
 upgrade tool</a>,
-<a href="http://nodejs.org/download/">download a new version of Node</a>,
+<a href="https://nodejs.org/en/download/">download a new version of Node</a>,
 or follow the Windows upgrade instructions in the
 <a href="https://github.com/npm/npm/wiki/Troubleshooting#upgrading-on-windows">npm Troubleshooting Guide</a>.</p>
 <p>If that&#39;s not fancy enough for you, then you can fetch the code with
@@ -126,5 +126,5 @@ <h2 id="see-also">SEE ALSO</h2>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer"><a href="../doc/README.html">README</a> &mdash; npm@4.1.2</p>
+<p id="footer"><a href="../doc/README.html">README</a> &mdash; npm@4.2.0</p>
 
diff --git a/deps/npm/html/doc/cli/npm-access.html b/deps/npm/html/doc/cli/npm-access.html
@@ -84,5 +84,5 @@ <h2 id="see-also">SEE ALSO</h2>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-access &mdash; npm@4.1.2</p>
+<p id="footer">npm-access &mdash; npm@4.2.0</p>
 
diff --git a/deps/npm/html/doc/cli/npm-adduser.html b/deps/npm/html/doc/cli/npm-adduser.html
@@ -73,5 +73,5 @@ <h2 id="see-also">SEE ALSO</h2>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-adduser &mdash; npm@4.1.2</p>
+<p id="footer">npm-adduser &mdash; npm@4.2.0</p>
 
diff --git a/deps/npm/html/doc/cli/npm-bin.html b/deps/npm/html/doc/cli/npm-bin.html
@@ -35,5 +35,5 @@ <h2 id="see-also">SEE ALSO</h2>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-bin &mdash; npm@4.1.2</p>
+<p id="footer">npm-bin &mdash; npm@4.2.0</p>
 
diff --git a/deps/npm/html/doc/cli/npm-bugs.html b/deps/npm/html/doc/cli/npm-bugs.html
@@ -55,5 +55,5 @@ <h2 id="see-also">SEE ALSO</h2>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-bugs &mdash; npm@4.1.2</p>
+<p id="footer">npm-bugs &mdash; npm@4.2.0</p>
 
diff --git a/deps/npm/html/doc/cli/npm-build.html b/deps/npm/html/doc/cli/npm-build.html
@@ -40,5 +40,5 @@ <h2 id="description">DESCRIPTION</h2>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-build &mdash; npm@4.1.2</p>
+<p id="footer">npm-build &mdash; npm@4.2.0</p>
 
diff --git a/deps/npm/html/doc/cli/npm-bundle.html b/deps/npm/html/doc/cli/npm-bundle.html
@@ -31,5 +31,5 @@ <h2 id="see-also">SEE ALSO</h2>
 <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
 <tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
 </table>
-<p id="footer">npm-bundle &mdash; npm@4.1.2</p>
+<p id="footer">npm-bundle &mdash; npm@4.2.0</p>