deps: upgrade npm to 4.2.0

PR-URL: https://github.com/nodejs/node/pull/11389
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>

11 files changed, 51 insertions, 32 deletions

diff --git a/deps/npm/html/doc/misc/npm-coding-style.html b/deps/npm/html/doc/misc/npm-coding-style.html
index f56c3dfc34..840d6274b1 100644
--- a/deps/npm/html/doc/misc/npm-coding-style.html
+++ b/deps/npm/html/doc/misc/npm-coding-style.html
@@ -153,5 +153,5 @@ set to anything.&quot;</p>
 <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-coding-style &mdash; npm@4.1.2</p>
+<p id="footer">npm-coding-style &mdash; npm@4.2.0</p>
 
diff --git a/deps/npm/html/doc/misc/npm-config.html b/deps/npm/html/doc/misc/npm-config.html
index f6ba450b1a..666f6d4b01 100644
--- a/deps/npm/html/doc/misc/npm-config.html
+++ b/deps/npm/html/doc/misc/npm-config.html
@@ -497,6 +497,12 @@ programmatically, you may wish to send logs to somewhere other than
 stderr.</p>
 <p>If the <code>color</code> config is set to true, then this stream will receive
 colored output if it is a TTY.</p>
+<h3 id="logs-max">logs-max</h3>
+<ul>
+<li>Default: 10</li>
+<li>Type: Number</li>
+</ul>
+<p>The maximum number of log files to store.</p>
 <h3 id="long">long</h3>
 <ul>
 <li>Default: false</li>
@@ -722,12 +728,20 @@ first on the <code>PATH</code> are different.</p>
 <li>Type: String</li>
 </ul>
 <p>Space-separated options that are always passed to search.</p>
+<h3 id="searchlimit">searchlimit</h3>
+<ul>
+<li>Default: 20</li>
+<li>Type: Number</li>
+</ul>
+<p>Number of items to limit search results to. Will not apply at all to legacy
+searches.</p>
 <h3 id="searchstaleness">searchstaleness</h3>
 <ul>
 <li>Default: 900 (15 minutes)</li>
 <li>Type: Number</li>
 </ul>
-<p>The age of the cache, in seconds, before another registry request is made.</p>
+<p>The age of the cache, in seconds, before another registry request is made if
+using legacy search endpoint.</p>
 <h3 id="send-metrics">send-metrics</h3>
 <ul>
 <li>Default: false</li>
@@ -887,5 +901,5 @@ exit successfully.</p>
 <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-config &mdash; npm@4.1.2</p>
+<p id="footer">npm-config &mdash; npm@4.2.0</p>
 
diff --git a/deps/npm/html/doc/misc/npm-developers.html b/deps/npm/html/doc/misc/npm-developers.html
index b0b07a936f..13b0c3d14f 100644
--- a/deps/npm/html/doc/misc/npm-developers.html
+++ b/deps/npm/html/doc/misc/npm-developers.html
@@ -194,5 +194,5 @@ from a fresh checkout.</p>
 <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-developers &mdash; npm@4.1.2</p>
+<p id="footer">npm-developers &mdash; npm@4.2.0</p>
 
diff --git a/deps/npm/html/doc/misc/npm-disputes.html b/deps/npm/html/doc/misc/npm-disputes.html
index 3add632e0d..731f73ff1d 100644
--- a/deps/npm/html/doc/misc/npm-disputes.html
+++ b/deps/npm/html/doc/misc/npm-disputes.html
@@ -20,7 +20,7 @@ Conduct.</p>
 <h2 id="tl-dr">TL;DR</h2>
 <ol>
 <li>Get the author email with <code>npm owner ls &lt;pkgname&gt;</code></li>
-<li>Email the author, CC <a href="&#x6d;&#x61;&#x69;&#x6c;&#x74;&#x6f;&#x3a;&#115;&#x75;&#112;&#x70;&#x6f;&#114;&#116;&#64;&#110;&#112;&#x6d;&#106;&#x73;&#x2e;&#x63;&#x6f;&#x6d;">&#115;&#x75;&#112;&#x70;&#x6f;&#114;&#116;&#64;&#110;&#112;&#x6d;&#106;&#x73;&#x2e;&#x63;&#x6f;&#x6d;</a></li>
+<li>Email the author, CC <a href="&#109;&#97;&#105;&#108;&#116;&#111;&#x3a;&#x73;&#117;&#x70;&#112;&#111;&#x72;&#x74;&#64;&#x6e;&#112;&#109;&#106;&#115;&#46;&#99;&#111;&#x6d;">&#x73;&#117;&#x70;&#112;&#111;&#x72;&#x74;&#64;&#x6e;&#112;&#109;&#106;&#115;&#46;&#99;&#111;&#x6d;</a></li>
 <li>After a few weeks, if there&#39;s no resolution, we&#39;ll sort it out.</li>
 </ol>
 <p>Don&#39;t squat on package names.  Publish code or move out of the way.</p>
@@ -55,12 +55,12 @@ because Yusuf&#39;s <code>foo</code> is in the way.</p>
 </li>
 <li>Alice emails Yusuf, explaining the situation <strong>as respectfully as possible</strong>,
 and what she would like to do with the module name. She adds the npm support
-staff <a href="&#109;&#x61;&#105;&#108;&#x74;&#111;&#58;&#115;&#117;&#x70;&#112;&#111;&#x72;&#x74;&#64;&#x6e;&#112;&#109;&#x6a;&#115;&#46;&#x63;&#111;&#109;">&#115;&#117;&#x70;&#112;&#111;&#x72;&#x74;&#64;&#x6e;&#112;&#109;&#x6a;&#115;&#46;&#x63;&#111;&#109;</a> to the CC list of the email. Mention in the email
+staff <a href="&#109;&#97;&#x69;&#108;&#x74;&#111;&#x3a;&#x73;&#117;&#x70;&#x70;&#x6f;&#x72;&#116;&#x40;&#110;&#112;&#109;&#x6a;&#x73;&#x2e;&#x63;&#111;&#109;">&#x73;&#117;&#x70;&#x70;&#x6f;&#x72;&#116;&#x40;&#110;&#112;&#109;&#x6a;&#x73;&#x2e;&#x63;&#111;&#109;</a> to the CC list of the email. Mention in the email
 that Yusuf can run npm owner <code>add alice foo</code> to add Alice as an owner of the
 foo package.</li>
 <li>After a reasonable amount of time, if Yusuf has not responded, or if Yusuf
 and Alice can&#39;t come to any sort of resolution, email support
-<a href="&#109;&#97;&#105;&#108;&#x74;&#111;&#x3a;&#x73;&#117;&#x70;&#x70;&#111;&#114;&#116;&#x40;&#110;&#112;&#109;&#x6a;&#115;&#46;&#99;&#111;&#x6d;">&#x73;&#117;&#x70;&#x70;&#111;&#114;&#116;&#x40;&#110;&#112;&#109;&#x6a;&#115;&#46;&#99;&#111;&#x6d;</a> and we&#39;ll sort it out. (&quot;Reasonable&quot; is usually at least
+<a href="&#x6d;&#x61;&#105;&#x6c;&#116;&#111;&#x3a;&#x73;&#117;&#x70;&#x70;&#x6f;&#114;&#x74;&#64;&#110;&#112;&#109;&#x6a;&#x73;&#x2e;&#x63;&#111;&#x6d;">&#x73;&#117;&#x70;&#x70;&#x6f;&#114;&#x74;&#64;&#110;&#112;&#109;&#x6a;&#x73;&#x2e;&#x63;&#111;&#x6d;</a> and we&#39;ll sort it out. (&quot;Reasonable&quot; is usually at least
 4 weeks.)</li>
 </ol>
 <h2 id="reasoning">REASONING</h2>
@@ -96,12 +96,12 @@ application database or otherwise putting non-packagey things into it.</li>
 <a href="https://www.npmjs.com/policies/conduct">Code of Conduct</a> such as hateful
 language, pornographic content, or harassment.</li>
 </ol>
-<p>If you see bad behavior like this, please report it to <a href="&#109;&#97;&#105;&#108;&#x74;&#x6f;&#58;&#97;&#x62;&#117;&#115;&#x65;&#64;&#x6e;&#112;&#109;&#x6a;&#x73;&#x2e;&#99;&#x6f;&#109;">&#97;&#x62;&#117;&#115;&#x65;&#64;&#x6e;&#112;&#109;&#x6a;&#x73;&#x2e;&#99;&#x6f;&#109;</a> right
+<p>If you see bad behavior like this, please report it to <a href="&#109;&#97;&#105;&#x6c;&#x74;&#x6f;&#x3a;&#97;&#98;&#117;&#x73;&#101;&#64;&#x6e;&#x70;&#x6d;&#106;&#115;&#x2e;&#x63;&#111;&#x6d;">&#97;&#98;&#117;&#x73;&#101;&#64;&#x6e;&#x70;&#x6d;&#106;&#115;&#x2e;&#x63;&#111;&#x6d;</a> right
 away. <strong>You are never expected to resolve abusive behavior on your own. We are
 here to help.</strong></p>
 <h2 id="trademarks">TRADEMARKS</h2>
 <p>If you think another npm publisher is infringing your trademark, such as by
-using a confusingly similar package name, email <a href="&#x6d;&#x61;&#x69;&#108;&#x74;&#111;&#58;&#97;&#x62;&#x75;&#115;&#x65;&#64;&#x6e;&#112;&#x6d;&#106;&#115;&#46;&#x63;&#111;&#x6d;">&#97;&#x62;&#x75;&#115;&#x65;&#64;&#x6e;&#112;&#x6d;&#106;&#115;&#46;&#x63;&#111;&#x6d;</a> with a link to
+using a confusingly similar package name, email <a href="&#109;&#x61;&#x69;&#x6c;&#x74;&#111;&#x3a;&#x61;&#98;&#x75;&#115;&#101;&#x40;&#x6e;&#x70;&#109;&#106;&#x73;&#46;&#x63;&#x6f;&#x6d;">&#x61;&#98;&#x75;&#115;&#101;&#x40;&#x6e;&#x70;&#109;&#106;&#x73;&#46;&#x63;&#x6f;&#x6d;</a> with a link to
 the package or user account on <a href="https://npmjs.com">https://npmjs.com</a>. Attach a
 copy of your trademark registration certificate.</p>
 <p>If we see that the package&#39;s publisher is intentionally misleading others by
@@ -134,5 +134,5 @@ License.</p>
 <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-disputes &mdash; npm@4.1.2</p>
+<p id="footer">npm-disputes &mdash; npm@4.2.0</p>
 
diff --git a/deps/npm/html/doc/misc/npm-index.html b/deps/npm/html/doc/misc/npm-index.html
index 171efc448f..c3a177c3b0 100644
--- a/deps/npm/html/doc/misc/npm-index.html
+++ b/deps/npm/html/doc/misc/npm-index.html
@@ -162,5 +162,5 @@
 <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-index &mdash; npm@4.1.2</p>
+<p id="footer">npm-index &mdash; npm@4.2.0</p>
 
diff --git a/deps/npm/html/doc/misc/npm-orgs.html b/deps/npm/html/doc/misc/npm-orgs.html
index 57a40ca7e7..295839e289 100644
--- a/deps/npm/html/doc/misc/npm-orgs.html
+++ b/deps/npm/html/doc/misc/npm-orgs.html
@@ -86,5 +86,5 @@
 <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-orgs &mdash; npm@4.1.2</p>
+<p id="footer">npm-orgs &mdash; npm@4.2.0</p>
 
diff --git a/deps/npm/html/doc/misc/npm-registry.html b/deps/npm/html/doc/misc/npm-registry.html
index 727c174dfd..79eb492303 100644
--- a/deps/npm/html/doc/misc/npm-registry.html
+++ b/deps/npm/html/doc/misc/npm-registry.html
@@ -90,5 +90,5 @@ effectively implement the entire CouchDB API anyway.</p>
 <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-registry &mdash; npm@4.1.2</p>
+<p id="footer">npm-registry &mdash; npm@4.2.0</p>
 
diff --git a/deps/npm/html/doc/misc/npm-scope.html b/deps/npm/html/doc/misc/npm-scope.html
index 109e68c0f7..eab13e7beb 100644
--- a/deps/npm/html/doc/misc/npm-scope.html
+++ b/deps/npm/html/doc/misc/npm-scope.html
@@ -12,47 +12,51 @@
 <h1><a href="../misc/npm-scope.html">npm-scope</a></h1> <p>Scoped packages</p>
 <h2 id="description">DESCRIPTION</h2>
 <p>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.</p>
+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 <code>@</code> symbol
+and followed by a slash, e.g.</p>
 <pre><code>@somescope/somepackagename
 </code></pre><p>Scopes are a way of grouping related packages together, and also affect a few
 things about the way npm treats the package.</p>
+<p>Each npm user/organization has their own scope, and only you can add packages
+in your scope. This means you don&#39;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.</p>
 <p>Scoped packages can be published and installed as of <code>npm@2</code> 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.</p>
+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.</p>
 <h2 id="installing-scoped-packages">Installing scoped packages</h2>
 <p>Scoped packages are installed to a sub-folder of the regular installation
 folder, e.g. if your other packages are installed in <code>node_modules/packagename</code>,
-scoped modules will be in <code>node_modules/@myorg/packagename</code>. The scope folder
-(<code>@myorg</code>) is simply the name of the scope preceded by an @-symbol, and can
+scoped modules will be installed in <code>node_modules/@myorg/packagename</code>. The scope
+folder (<code>@myorg</code>) is simply the name of the scope preceded by an <code>@</code> symbol, and can
 contain any number of scoped packages.</p>
 <p>A scoped package is installed by referencing it by name, preceded by an
-@-symbol, in <code>npm install</code>:</p>
+<code>@</code> symbol, in <code>npm install</code>:</p>
 <pre><code>npm install @myorg/mypackage
 </code></pre><p>Or in <code>package.json</code>:</p>
 <pre><code>&quot;dependencies&quot;: {
   &quot;@myorg/mypackage&quot;: &quot;^1.3.0&quot;
 }
-</code></pre><p>Note that if the @-symbol is omitted in either case npm will instead attempt to
+</code></pre><p>Note that if the <code>@</code> symbol is omitted, in either case, npm will instead attempt to
 install from GitHub; see <code><a href="../cli/npm-install.html">npm-install(1)</a></code>.</p>
 <h2 id="requiring-scoped-packages">Requiring scoped packages</h2>
 <p>Because scoped packages are installed into a scope folder, you have to
 include the name of the scope when requiring them in your code, e.g.</p>
 <pre><code>require(&#39;@myorg/mypackage&#39;)
-</code></pre><p>There is nothing special about the way Node treats scope folders, this is
-just specifying to require the module <code>mypackage</code> in the folder called <code>@myorg</code>.</p>
+</code></pre><p>There is nothing special about the way Node treats scope folders. This
+simply requires the <code>mypackage</code> module in the folder named <code>@myorg</code>.</p>
 <h2 id="publishing-scoped-packages">Publishing scoped packages</h2>
 <p>Scoped packages can be published from the CLI as of <code>npm@2</code> and can be
 published to any registry that supports them, including the primary npm
 registry.</p>
 <p>(As of 2015-04-19, and with npm 2.0 or better, the primary npm registry
-<strong>does</strong> support scoped packages)</p>
+<strong>does</strong> support scoped packages.)</p>
 <p>If you wish, you may associate a scope with a registry; see below.</p>
 <h3 id="publishing-public-scoped-packages-to-the-primary-npm-registry">Publishing public scoped packages to the primary npm registry</h3>
 <p>To publish a public scoped package, you must specify <code>--access public</code> with
-the initial publication.  This will publish the package and set access
+the initial publication. This will publish the package and set access
 to <code>public</code> as if you had run <code>npm access public</code> after publishing.</p>
 <h3 id="publishing-private-scoped-packages-to-the-npm-registry">Publishing private scoped packages to the npm registry</h3>
 <p>To publish a private scoped package to the npm registry, you must have
@@ -60,7 +64,7 @@ an <a href="https://www.npmjs.com/private-modules">npm Private Modules</a>
 account.</p>
 <p>You can then publish the module with <code>npm publish</code> or <code>npm publish
 --access restricted</code>, 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 <code>npm access</code> or on the npmjs.com website.</p>
 <h2 id="associating-a-scope-with-a-registry">Associating a scope with a registry</h2>
 <p>Scopes can be associated with a separate registry. This allows you to
@@ -81,6 +85,7 @@ that registry instead.</p>
 <li><a href="../cli/npm-install.html">npm-install(1)</a></li>
 <li><a href="../cli/npm-publish.html">npm-publish(1)</a></li>
 <li><a href="../cli/npm-access.html">npm-access(1)</a></li>
+<li><a href="../misc/npm-registry.html">npm-registry(7)</a></li>
 </ul>
 
 </div>
@@ -94,5 +99,5 @@ that registry instead.</p>
 <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-scope &mdash; npm@4.1.2</p>
+<p id="footer">npm-scope &mdash; npm@4.2.0</p>
 
diff --git a/deps/npm/html/doc/misc/npm-scripts.html b/deps/npm/html/doc/misc/npm-scripts.html
index 453e76035e..3b37178494 100644
--- a/deps/npm/html/doc/misc/npm-scripts.html
+++ b/deps/npm/html/doc/misc/npm-scripts.html
@@ -237,5 +237,5 @@ scripts is for compilation which must be done on the target architecture.</li>
 <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-scripts &mdash; npm@4.1.2</p>
+<p id="footer">npm-scripts &mdash; npm@4.2.0</p>
 
diff --git a/deps/npm/html/doc/misc/removing-npm.html b/deps/npm/html/doc/misc/removing-npm.html
index b04d851e01..aeaea468d1 100644
--- a/deps/npm/html/doc/misc/removing-npm.html
+++ b/deps/npm/html/doc/misc/removing-npm.html
@@ -57,5 +57,5 @@ modules.  To track those down, you can do the following:</p>
 <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">removing-npm &mdash; npm@4.1.2</p>
+<p id="footer">removing-npm &mdash; npm@4.2.0</p>
 
diff --git a/deps/npm/html/doc/misc/semver.html b/deps/npm/html/doc/misc/semver.html
index dcee1f356d..48dee7d64b 100644
--- a/deps/npm/html/doc/misc/semver.html
+++ b/deps/npm/html/doc/misc/semver.html
@@ -325,5 +325,5 @@ range, use the <code>satisfies(version, range)</code> function.</p>
 <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">semver &mdash; npm@4.1.2</p>
+<p id="footer">semver &mdash; npm@4.2.0</p>