diff options
Diffstat (limited to 'deps/npm/html/doc/README.html')
| -rw-r--r-- | deps/npm/html/doc/README.html | 29 |
1 files changed, 11 insertions, 18 deletions
diff --git a/deps/npm/html/doc/README.html b/deps/npm/html/doc/README.html index f7a482f465..af5ea2e683 100644 --- a/deps/npm/html/doc/README.html +++ b/deps/npm/html/doc/README.html @@ -13,7 +13,7 @@ <p><a href="https://travis-ci.org/npm/npm"><img src="https://img.shields.io/travis/npm/npm/latest.svg" alt="Build Status"></a></p> <h2 id="synopsis">SYNOPSIS</h2> <p>This is just enough info to get you up and running.</p> -<p>Much more info available via <code>npm help</code> once it's installed.</p> +<p>Much more info will be available via <code>npm help</code> once it's installed.</p> <h2 id="important">IMPORTANT</h2> <p><strong>You need node v6 or higher to run this program.</strong></p> <p>To install an old <strong>and unsupported</strong> version of npm that works on node v5 @@ -40,15 +40,12 @@ paths, etc.) then read on.</p> <p>There's a pretty robust install script at <a href="https://www.npmjs.com/install.sh">https://www.npmjs.com/install.sh</a>. You can download that and run it.</p> <p>Here's an example using curl:</p> -<pre><code class="lang-sh">curl -L https://www.npmjs.com/install.sh | sh -</code></pre> +<pre><code class="language-sh">curl -L https://www.npmjs.com/install.sh | sh</code></pre> <h3 id="slightly-fancier">Slightly Fancier</h3> <p>You can set any npm configuration params with that script:</p> -<pre><code class="lang-sh">npm_config_prefix=/some/path sh install.sh -</code></pre> +<pre><code class="language-sh">npm_config_prefix=/some/path sh install.sh</code></pre> <p>Or, you can run it in uber-debuggery mode:</p> -<pre><code class="lang-sh">npm_debug=1 sh install.sh -</code></pre> +<pre><code class="language-sh">npm_debug=1 sh install.sh</code></pre> <h3 id="even-fancier">Even Fancier</h3> <p>Get the code with git. Use <code>make</code> to build the docs and do other stuff. If you plan on hacking on npm, <code>make link</code> is your friend.</p> @@ -69,11 +66,9 @@ git, and mess with it directly.</p> <p>No.</p> <h2 id="uninstalling">Uninstalling</h2> <p>So sad to see you go.</p> -<pre><code class="lang-sh">sudo npm uninstall npm -g -</code></pre> +<pre><code class="language-sh">sudo npm uninstall npm -g</code></pre> <p>Or, if that fails,</p> -<pre><code class="lang-sh">sudo make uninstall -</code></pre> +<pre><code class="language-sh">sudo make uninstall</code></pre> <h2 id="more-severe-uninstalling">More Severe Uninstalling</h2> <p>Usually, the above instructions are sufficient. That will remove npm, but leave behind anything you've installed.</p> @@ -82,13 +77,11 @@ then you can use the <code>npm ls</code> command to find them, and then <code>np remove them.</p> <p>To remove cruft left behind by npm 0.x, you can use the included <code>clean-old.sh</code> script file. You can run it conveniently like this:</p> -<pre><code class="lang-sh">npm explore npm -g -- sh scripts/clean-old.sh -</code></pre> +<pre><code class="language-sh">npm explore npm -g -- sh scripts/clean-old.sh</code></pre> <p>npm uses two configuration files, one for per-user configs, and another for global (every-user) configs. You can view them by doing:</p> -<pre><code class="lang-sh">npm config get userconfig # defaults to ~/.npmrc -npm config get globalconfig # defaults to /usr/local/etc/npmrc -</code></pre> +<pre><code class="language-sh">npm config get userconfig # defaults to ~/.npmrc +npm config get globalconfig # defaults to /usr/local/etc/npmrc</code></pre> <p>Uninstalling npm does not remove configuration files by default. You must remove them yourself manually if you want them gone. Note that this means that future npm installs will not remember the settings that @@ -102,7 +95,7 @@ you should <a href="https://docs.npmjs.com/misc/developers">read this</a>.</p> <p>When you find issues, please report them:</p> <ul> <li>web: -<a href="https://github.com/npm/npm/issues">https://github.com/npm/npm/issues</a></li> +<a href="https://npm.community/c/bugs">https://npm.community/c/bugs</a></li> </ul> <p>Be sure to include <em>all</em> of the output from the npm command that didn't work as expected. The <code>npm-debug.log</code> file is also helpful to provide.</p> @@ -127,5 +120,5 @@ doubt tell you to put the output in a gist or email.</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"><a href="../doc/README.html">README</a> — npm@6.1.0</p> +<p id="footer"><a href="../doc/README.html">README</a> — npm@6.2.0</p> |