npm: upgrade to 1.4.10

* Don't set referer if already set
* fetch: Send referer and npm-session headers
* run-script: Support --parseable and --json
* list runnable scripts (Evan Lucas)
* Use marked instead of ronn for html docs

1 files changed, 35 insertions, 31 deletions

diff --git a/deps/npm/html/doc/cli/npm-cache.html b/deps/npm/html/doc/cli/npm-cache.html
index f31c4d0bef..1d0d0805c6 100644
--- a/deps/npm/html/doc/cli/npm-cache.html
+++ b/deps/npm/html/doc/cli/npm-cache.html
@@ -10,9 +10,7 @@
     <div id="wrapper">
 
 <h1><a href="../cli/npm-cache.html">npm-cache</a></h1> <p>Manipulates packages cache</p>
-
-<h2 id="SYNOPSIS">SYNOPSIS</h2>
-
+<h2 id="synopsis">SYNOPSIS</h2>
 <pre><code>npm cache add &lt;tarball file&gt;
 npm cache add &lt;folder&gt;
 npm cache add &lt;tarball url&gt;
@@ -20,54 +18,60 @@ npm cache add &lt;name&gt;@&lt;version&gt;
 
 npm cache ls [&lt;path&gt;]
 
-npm cache clean [&lt;path&gt;]</code></pre>
-
-<h2 id="DESCRIPTION">DESCRIPTION</h2>
-
+npm cache clean [&lt;path&gt;]
+</code></pre><h2 id="description">DESCRIPTION</h2>
 <p>Used to add, list, or clear the npm cache folder.</p>
-
-<ul><li><p>add:
+<ul>
+<li><p>add:
 Add the specified package to the local cache.  This command is primarily
 intended to be used internally by npm, but it can provide a way to
-add data to the local installation cache explicitly.</p></li><li><p>ls:
+add data to the local installation cache explicitly.</p>
+</li>
+<li><p>ls:
 Show the data in the cache.  Argument is a path to show in the cache
 folder.  Works a bit like the <code>find</code> program, but limited by the
-<code>depth</code> config.</p></li><li><p>clean:
+<code>depth</code> config.</p>
+</li>
+<li><p>clean:
 Delete data out of the cache folder.  If an argument is provided, then
 it specifies a subpath to delete.  If no argument is provided, then
-the entire cache is cleared.</p></li></ul>
-
-<h2 id="DETAILS">DETAILS</h2>
-
+the entire cache is cleared.</p>
+</li>
+</ul>
+<h2 id="details">DETAILS</h2>
 <p>npm stores cache data in the directory specified in <code>npm config get cache</code>.
 For each package that is added to the cache, three pieces of information are
 stored in <code>{cache}/{name}/{version}</code>:</p>
-
-<ul><li>.../package/:
-A folder containing the package contents as they appear in the tarball.</li><li>.../package.json:
-The package.json file, as npm sees it, with overlays applied and a _id attribute.</li><li>.../package.tgz:
-The tarball for that version.</li></ul>
-
+<ul>
+<li>.../package/:
+A folder containing the package contents as they appear in the tarball.</li>
+<li>.../package.json:
+The package.json file, as npm sees it, with overlays applied and a _id attribute.</li>
+<li>.../package.tgz:
+The tarball for that version.</li>
+</ul>
 <p>Additionally, whenever a registry request is made, a <code>.cache.json</code> file
 is placed at the corresponding URI, to store the ETag and the requested
 data.</p>
-
 <p>Commands that make non-essential registry requests (such as <code>search</code> and
 <code>view</code>, or the completion scripts) generally specify a minimum timeout.
 If the <code>.cache.json</code> file is younger than the specified timeout, then
 they do not make an HTTP request to the registry.</p>
-
-<h2 id="CONFIGURATION">CONFIGURATION</h2>
-
+<h2 id="configuration">CONFIGURATION</h2>
 <h3 id="cache">cache</h3>
-
 <p>Default: <code>~/.npm</code> on Posix, or <code>%AppData%/npm-cache</code> on Windows.</p>
-
 <p>The root cache folder.</p>
+<h2 id="see-also">SEE ALSO</h2>
+<ul>
+<li><a href="../files/npm-folders.html">npm-folders(5)</a></li>
+<li><a href="../cli/npm-config.html">npm-config(1)</a></li>
+<li><a href="../misc/npm-config.html">npm-config(7)</a></li>
+<li><a href="../files/npmrc.html">npmrc(5)</a></li>
+<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-pack.html">npm-pack(1)</a></li>
+</ul>
 
-<h2 id="SEE-ALSO">SEE ALSO</h2>
-
-<ul><li><a href="../files/npm-folders.html">npm-folders(5)</a></li><li><a href="../cli/npm-config.html">npm-config(1)</a></li><li><a href="../misc/npm-config.html">npm-config(7)</a></li><li><a href="../files/npmrc.html">npmrc(5)</a></li><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-pack.html">npm-pack(1)</a></li></ul>
 </div>
 
 <table border=0 cellspacing=0 cellpadding=0 id=npmlogo>
@@ -79,5 +83,5 @@ they do not make an HTTP request to the registry.</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-cache &mdash; npm@1.4.9</p>
+<p id="footer">npm-cache &mdash; npm@1.4.10</p>