diff options
Diffstat (limited to 'deps/npm/html/doc/cli/npm-doctor.html')
| -rw-r--r-- | deps/npm/html/doc/cli/npm-doctor.html | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/deps/npm/html/doc/cli/npm-doctor.html b/deps/npm/html/doc/cli/npm-doctor.html index 92ca7d5122..8eba9f172d 100644 --- a/deps/npm/html/doc/cli/npm-doctor.html +++ b/deps/npm/html/doc/cli/npm-doctor.html @@ -32,7 +32,7 @@ old versions of npm. Since npm is constantly improving, running <code>npm@latest better than an old version.</p> <p><code>npm doctor</code> verifies the following items in your environment, and if there are any recommended changes, it will display them.</p> -<h3 id="npm-ping"><code>npm ping</code></h3> +<h3 id="-npm-ping-"><code>npm ping</code></h3> <p>By default, npm installs from the primary npm registry, <code>registry.npmjs.org</code>. <code>npm doctor</code> hits a special ping endpoint within the registry. This can also be checked with <code>npm ping</code>. If this check fails, you may be using a proxy that @@ -42,7 +42,7 @@ HTTPS to <code>registry.npmjs.org</code>.</p> what that is by running <code>npm config get registry</code>), and if you're using a private registry that doesn't support the <code>/whoami</code> endpoint supported by the primary registry, this check may fail.</p> -<h3 id="npm-v"><code>npm -v</code></h3> +<h3 id="-npm-v-"><code>npm -v</code></h3> <p>While Node.js may come bundled with a particular version of npm, it's the policy of the CLI team that we recommend all users run <code>npm@latest</code> if they can. As the CLI is maintained by a small team of contributors, there are only @@ -50,21 +50,21 @@ resources for a single line of development, so npm's own long-term support releases typically only receive critical security and regression fixes. The team believes that the latest tested version of npm is almost always likely to be the most functional and defect-free version of npm.</p> -<h3 id="node-v"><code>node -v</code></h3> +<h3 id="-node-v-"><code>node -v</code></h3> <p>For most users, in most circumstances, the best version of Node will be the latest long-term support (LTS) release. Those of you who want access to new ECMAscript features or bleeding-edge changes to Node's standard library may be running a newer version, and some of you may be required to run an older version of Node because of enterprise change control policies. That's OK! But in general, the npm team recommends that most users run Node.js LTS.</p> -<h3 id="npm-config-get-registry"><code>npm config get registry</code></h3> +<h3 id="-npm-config-get-registry-"><code>npm config get registry</code></h3> <p>Some of you may be installing from private package registries for your project or company. That's great! Others of you may be following tutorials or StackOverflow questions in an effort to troubleshoot problems you may be having. Sometimes, this may entail changing the registry you're pointing at. This part of <code>npm doctor</code> just lets you, and maybe whoever's helping you with support, know that you're not using the default registry.</p> -<h3 id="which-git"><code>which git</code></h3> +<h3 id="-which-git-"><code>which git</code></h3> <p>While it's documented in the <a href="../../doc/README.html">README</a>, it may not be obvious that npm needs Git installed to do many of the things that it does. Also, in some cases – especially on Windows – you may have Git set up in such a way that it's not @@ -103,4 +103,4 @@ cache, you should probably run <code>npm cache clean</code> and reset the cache. <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-doctor — npm@5.8.0</p> +<p id="footer">npm-doctor — npm@5.6.0</p> |