diff options
Diffstat (limited to 'deps/npm/html/doc/cli/npm-install.html')
-rw-r--r-- | deps/npm/html/doc/cli/npm-install.html | 12 |
1 files changed, 10 insertions, 2 deletions
diff --git a/deps/npm/html/doc/cli/npm-install.html b/deps/npm/html/doc/cli/npm-install.html index 5989cc25a1..5bc9cd985b 100644 --- a/deps/npm/html/doc/cli/npm-install.html +++ b/deps/npm/html/doc/cli/npm-install.html @@ -54,6 +54,10 @@ after packing it up into a tarball (b).</p> <p> With the <code>--production</code> flag (or when the <code>NODE_ENV</code> environment variable is set to <code>production</code>), npm will not install modules listed in <code>devDependencies</code>.</p> +<blockquote> +<p>NOTE: The <code>--production</code> flag has no particular meaning when adding a + dependency to a project.</p> +</blockquote> </li> <li><p><code>npm install <folder></code>:</p> <p> Install the package in the directory as a symlink in the current project. @@ -281,11 +285,14 @@ being installed.</p> <p>The <code>--no-shrinkwrap</code> argument, which will ignore an available package lock or shrinkwrap file and use the package.json instead.</p> <p>The <code>--no-package-lock</code> argument will prevent npm from creating a -<code>package-lock.json</code> file.</p> +<code>package-lock.json</code> file. When running with package-lock's disabled npm +will not automatically prune your node modules when installing.</p> <p>The <code>--nodedir=/path/to/node/source</code> argument will allow npm to find the node source code so that npm can compile native modules.</p> <p>The <code>--only={prod[uction]|dev[elopment]}</code> argument will cause either only <code>devDependencies</code> or only non-<code>devDependencies</code> to be installed regardless of the <code>NODE_ENV</code>.</p> +<p>The <code>--no-audit</code> argument can be used to disable sending of audit reports to +the configured registries. See <code><a href="../cli/npm-audit.html">npm-audit(1)</a></code> for details on what is sent.</p> <p>See <code><a href="../misc/npm-config.html">npm-config(7)</a></code>. Many of the configuration params have some effect on installation, since that's most of what npm does.</p> <h2 id="algorithm">ALGORITHM</h2> @@ -344,6 +351,7 @@ affects a real use-case, it will be investigated.</p> <ul> <li><a href="../files/npm-folders.html">npm-folders(5)</a></li> <li><a href="../cli/npm-update.html">npm-update(1)</a></li> +<li><a href="../cli/npm-audit.html">npm-audit(1)</a></li> <li><a href="../cli/npm-link.html">npm-link(1)</a></li> <li><a href="../cli/npm-rebuild.html">npm-rebuild(1)</a></li> <li><a href="../misc/npm-scripts.html">npm-scripts(7)</a></li> @@ -369,5 +377,5 @@ affects a real use-case, it will be investigated.</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-install — npm@5.6.0</p> +<p id="footer">npm-install — npm@6.1.0</p> |