diff options
Diffstat (limited to 'deps/npm/html/doc/cli/npm-outdated.html')
| -rw-r--r-- | deps/npm/html/doc/cli/npm-outdated.html | 57 |
1 files changed, 53 insertions, 4 deletions
diff --git a/deps/npm/html/doc/cli/npm-outdated.html b/deps/npm/html/doc/cli/npm-outdated.html index 69513a8d7b..0c007aa4b1 100644 --- a/deps/npm/html/doc/cli/npm-outdated.html +++ b/deps/npm/html/doc/cli/npm-outdated.html @@ -15,9 +15,56 @@ </code></pre><h2 id="description">DESCRIPTION</h2> <p>This command will check the registry to see if any (or, specific) installed packages are currently outdated.</p> -<p>The resulting field 'wanted' shows the latest version according to the -version specified in the package.json, the field 'latest' the very latest -version of the package.</p> +<p>In the output:</p> +<ul> +<li><code>wanted</code> is the maximum version of the package that satisfies the semver +range specified in <code>package.json</code>. If there's no available semver range (i.e. +you're running <code>npm outdated --global</code>, or the package isn't included in +<code>package.json</code>), then <code>wanted</code> shows the currently-installed version.</li> +<li><code>latest</code> is the version of the package tagged as latest in the registry. +Running <code>npm publish</code> with no special configuration will publish the package +with a dist-tag of <code>latest</code>. This may or may not be the maximum version of +the package, or the most-recently published version of the package, depending +on how the package's developer manages the latest <a href="../cli/dist-tag.html">dist-tag(1)</a>.</li> +<li><code>location</code> is where in the dependency tree the package is located. Note that +<code>npm outdated</code> defaults to a depth of 0, so unless you override that, you'll +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> +</ul> +<h3 id="an-example">An example</h3> +<pre><code>$ npm outdated +Package Current Wanted Latest Location +glob 5.0.15 5.0.15 6.0.1 test-outdated-output +nothingness 0.0.3 git git test-outdated-output +npm 3.5.1 3.5.2 3.5.1 test-outdated-output +local-dev 0.0.3 linked linked test-outdated-output +once 1.3.2 1.3.3 1.3.3 test-outdated-output +</code></pre><p>With these <code>dependencies</code>:</p> +<pre><code class="lang-json">{ + "glob": "^5.0.15", + "nothingness": "github:othiym23/nothingness#master", + "npm": "^3.5.1", + "once": "^1.3.1" +} +</code></pre> +<p>A few things to note:</p> +<ul> +<li><code>glob</code> requires <code>^5</code>, which prevents npm from installing <code>glob@6</code>, which is +outside the semver range.</li> +<li>Git dependencies will always be reinstalled, because of how they're specified. +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><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> <h2 id="configuration">CONFIGURATION</h2> <h3 id="json">json</h3> <ul> @@ -46,12 +93,14 @@ version of the package.</p> project.</p> <h3 id="depth">depth</h3> <ul> +<li>Default: 0</li> <li>Type: Int</li> </ul> <p>Max depth for checking dependency tree.</p> <h2 id="see-also">SEE ALSO</h2> <ul> <li><a href="../cli/npm-update.html">npm-update(1)</a></li> +<li><a href="../cli/npm-dist-tag.html">npm-dist-tag(1)</a></li> <li><a href="../misc/npm-registry.html">npm-registry(7)</a></li> <li><a href="../files/npm-folders.html">npm-folders(5)</a></li> </ul> @@ -67,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@3.3.12</p> +<p id="footer">npm-outdated — npm@3.6.0</p> |