diff options
Diffstat (limited to 'deps/npm/html/doc/cli/npm-outdated.html')
| -rw-r--r-- | deps/npm/html/doc/cli/npm-outdated.html | 10 |
1 files changed, 6 insertions, 4 deletions
diff --git a/deps/npm/html/doc/cli/npm-outdated.html b/deps/npm/html/doc/cli/npm-outdated.html index dc847796e8..fa4f463f82 100644 --- a/deps/npm/html/doc/cli/npm-outdated.html +++ b/deps/npm/html/doc/cli/npm-outdated.html @@ -31,6 +31,7 @@ always be seeing only top-level dependencies that are outdated.</li> <li><code>package type</code> (when using <code>--long</code> / <code>-l</code>) tells you whether this package is a <code>dependency</code> or a <code>devDependency</code>. Packages not included in <code>package.json</code> are always marked <code>dependencies</code>.</li> +<li><code>homepage</code> (when using <code>--long</code> / <code>-l</code>) is the <code>homepage</code> value contained in the package's <code>package.json</code></li> <li>Red means there's a newer version matching your semver requirements, so you should update now.</li> <li>Yellow indicates that there's a newer version above your semver requirements (usually new major, or new 0.x minor) so proceed with caution.</li> </ul> @@ -57,9 +58,10 @@ The installed committish might satisfy the dependency specifier (if it's something immutable, like a commit SHA), or it might not, so <code>npm outdated</code> and <code>npm update</code> have to fetch Git repos to check. This is why currently doing a reinstall of a Git dependency always forces a new clone and install.</li> -<li><a href="mailto:%60npm@3.5.2">`npm@3.5.2</a><code>is marked as "wanted", but "latest" is</code><a href="mailto:npm@3.5.1">npm@3.5.1</a><code>because npm -uses dist-tags to manage its</code>latest<code>and</code>next<code>release channels.</code>npm update<code>will install the _newest_ version, but</code>npm install npm<code>(with no semver range) -will install whatever's tagged as</code>latest`.</li> +<li><code>npm@3.5.2</code> is marked as "wanted", but "latest" is <code>npm@3.5.1</code> because npm +uses dist-tags to manage its <code>latest</code> and <code>next</code> release channels. <code>npm update</code> +will install the <em>newest</em> version, but <code>npm install npm</code> (with no semver range) +will install whatever's tagged as <code>latest</code>.</li> <li><code>once</code> is just plain out of date. Reinstalling <code>node_modules</code> from scratch or running <code>npm update</code> will bring it up to spec.</li> </ul> @@ -114,5 +116,5 @@ project.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-outdated — npm@6.4.1</p> +<p id="footer">npm-outdated — npm@6.5.0-next.0</p> |