1<!DOCTYPE html><html><head> 2<meta charset="utf-8"> 3<title>npm-install-test</title> 4<style> 5body { 6 background-color: #ffffff; 7 color: #24292e; 8 9 margin: 0; 10 11 line-height: 1.5; 12 13 font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji"; 14} 15#rainbar { 16 height: 10px; 17 background-image: linear-gradient(139deg, #fb8817, #ff4b01, #c12127, #e02aff); 18} 19 20a { 21 text-decoration: none; 22 color: #0366d6; 23} 24a:hover { 25 text-decoration: underline; 26} 27 28pre { 29 margin: 1em 0px; 30 padding: 1em; 31 border: solid 1px #e1e4e8; 32 border-radius: 6px; 33 34 display: block; 35 overflow: auto; 36 37 white-space: pre; 38 39 background-color: #f6f8fa; 40 color: #393a34; 41} 42code { 43 font-family: SFMono-Regular, Consolas, "Liberation Mono", Menlo, Courier, monospace; 44 font-size: 85%; 45 padding: 0.2em 0.4em; 46 background-color: #f6f8fa; 47 color: #393a34; 48} 49pre > code { 50 padding: 0; 51 background-color: inherit; 52 color: inherit; 53} 54h1, h2, h3 { 55 font-weight: 600; 56} 57 58#logobar { 59 background-color: #333333; 60 margin: 0 auto; 61 padding: 1em 4em; 62} 63#logobar .logo { 64 float: left; 65} 66#logobar .title { 67 font-weight: 600; 68 color: #dddddd; 69 float: left; 70 margin: 5px 0 0 1em; 71} 72#logobar:after { 73 content: ""; 74 display: block; 75 clear: both; 76} 77 78#content { 79 margin: 0 auto; 80 padding: 0 4em; 81} 82 83#table_of_contents > h2 { 84 font-size: 1.17em; 85} 86#table_of_contents ul:first-child { 87 border: solid 1px #e1e4e8; 88 border-radius: 6px; 89 padding: 1em; 90 background-color: #f6f8fa; 91 color: #393a34; 92} 93#table_of_contents ul { 94 list-style-type: none; 95 padding-left: 1.5em; 96} 97#table_of_contents li { 98 font-size: 0.9em; 99} 100#table_of_contents li a { 101 color: #000000; 102} 103 104header.title { 105 border-bottom: solid 1px #e1e4e8; 106} 107header.title > h1 { 108 margin-bottom: 0.25em; 109} 110header.title > .description { 111 display: block; 112 margin-bottom: 0.5em; 113 line-height: 1; 114} 115 116footer#edit { 117 border-top: solid 1px #e1e4e8; 118 margin: 3em 0 4em 0; 119 padding-top: 2em; 120} 121</style> 122</head> 123<body> 124<div id="banner"> 125<div id="rainbar"></div> 126<div id="logobar"> 127<svg class="logo" role="img" height="32" width="32" viewBox="0 0 700 700"> 128<polygon fill="#cb0000" points="0,700 700,700 700,0 0,0"></polygon> 129<polygon fill="#ffffff" points="150,550 350,550 350,250 450,250 450,550 550,550 550,150 150,150"></polygon> 130</svg> 131<div class="title"> 132npm command-line interface 133</div> 134</div> 135</div> 136 137<section id="content"> 138<header class="title"> 139<h1 id="npm-install-test">npm-install-test</h1> 140<span class="description">Install package(s) and run tests</span> 141</header> 142 143<section id="table_of_contents"> 144<h2 id="table-of-contents">Table of contents</h2> 145<div id="_table_of_contents"><ul><li><a href="#synopsis">Synopsis</a></li><li><a href="#description">Description</a></li><li><a href="#configuration">Configuration</a></li><ul><li><a href="#save"><code>save</code></a></li><li><a href="#save-exact"><code>save-exact</code></a></li><li><a href="#global"><code>global</code></a></li><li><a href="#install-strategy"><code>install-strategy</code></a></li><li><a href="#legacy-bundling"><code>legacy-bundling</code></a></li><li><a href="#global-style"><code>global-style</code></a></li><li><a href="#omit"><code>omit</code></a></li><li><a href="#strict-peer-deps"><code>strict-peer-deps</code></a></li><li><a href="#prefer-dedupe"><code>prefer-dedupe</code></a></li><li><a href="#package-lock"><code>package-lock</code></a></li><li><a href="#package-lock-only"><code>package-lock-only</code></a></li><li><a href="#foreground-scripts"><code>foreground-scripts</code></a></li><li><a href="#ignore-scripts"><code>ignore-scripts</code></a></li><li><a href="#audit"><code>audit</code></a></li><li><a href="#bin-links"><code>bin-links</code></a></li><li><a href="#fund"><code>fund</code></a></li><li><a href="#dry-run"><code>dry-run</code></a></li><li><a href="#workspace"><code>workspace</code></a></li><li><a href="#workspaces"><code>workspaces</code></a></li><li><a href="#include-workspace-root"><code>include-workspace-root</code></a></li><li><a href="#install-links"><code>install-links</code></a></li></ul><li><a href="#see-also">See Also</a></li></ul></div> 146</section> 147 148<div id="_content"><h3 id="synopsis">Synopsis</h3> 149<pre><code class="language-bash">npm install-test [<package-spec> ...] 150 151alias: it 152</code></pre> 153<h3 id="description">Description</h3> 154<p>This command runs an <code>npm install</code> followed immediately by an <code>npm test</code>. It 155takes exactly the same arguments as <code>npm install</code>.</p> 156<h3 id="configuration">Configuration</h3> 157<h4 id="save"><code>save</code></h4> 158<ul> 159<li>Default: <code>true</code> unless when using <code>npm update</code> where it defaults to <code>false</code></li> 160<li>Type: Boolean</li> 161</ul> 162<p>Save installed packages to a <code>package.json</code> file as dependencies.</p> 163<p>When used with the <code>npm rm</code> command, removes the dependency from 164<code>package.json</code>.</p> 165<p>Will also prevent writing to <code>package-lock.json</code> if set to <code>false</code>.</p> 166<h4 id="save-exact"><code>save-exact</code></h4> 167<ul> 168<li>Default: false</li> 169<li>Type: Boolean</li> 170</ul> 171<p>Dependencies saved to package.json will be configured with an exact version 172rather than using npm's default semver range operator.</p> 173<h4 id="global"><code>global</code></h4> 174<ul> 175<li>Default: false</li> 176<li>Type: Boolean</li> 177</ul> 178<p>Operates in "global" mode, so that packages are installed into the <code>prefix</code> 179folder instead of the current working directory. See 180<a href="../configuring-npm/folders.html">folders</a> for more on the differences in behavior.</p> 181<ul> 182<li>packages are installed into the <code>{prefix}/lib/node_modules</code> folder, instead 183of the current working directory.</li> 184<li>bin files are linked to <code>{prefix}/bin</code></li> 185<li>man pages are linked to <code>{prefix}/share/man</code></li> 186</ul> 187<h4 id="install-strategy"><code>install-strategy</code></h4> 188<ul> 189<li>Default: "hoisted"</li> 190<li>Type: "hoisted", "nested", "shallow", or "linked"</li> 191</ul> 192<p>Sets the strategy for installing packages in node_modules. hoisted 193(default): Install non-duplicated in top-level, and duplicated as necessary 194within directory structure. nested: (formerly --legacy-bundling) install in 195place, no hoisting. shallow (formerly --global-style) only install direct 196deps at top-level. linked: (experimental) install in node_modules/.store, 197link in place, unhoisted.</p> 198<h4 id="legacy-bundling"><code>legacy-bundling</code></h4> 199<ul> 200<li>Default: false</li> 201<li>Type: Boolean</li> 202<li>DEPRECATED: This option has been deprecated in favor of 203<code>--install-strategy=nested</code></li> 204</ul> 205<p>Instead of hoisting package installs in <code>node_modules</code>, install packages in 206the same manner that they are depended on. This may cause very deep 207directory structures and duplicate package installs as there is no 208de-duplicating. Sets <code>--install-strategy=nested</code>.</p> 209<h4 id="global-style"><code>global-style</code></h4> 210<ul> 211<li>Default: false</li> 212<li>Type: Boolean</li> 213<li>DEPRECATED: This option has been deprecated in favor of 214<code>--install-strategy=shallow</code></li> 215</ul> 216<p>Only install direct dependencies in the top level <code>node_modules</code>, but hoist 217on deeper dependencies. Sets <code>--install-strategy=shallow</code>.</p> 218<h4 id="omit"><code>omit</code></h4> 219<ul> 220<li>Default: 'dev' if the <code>NODE_ENV</code> environment variable is set to 221'production', otherwise empty.</li> 222<li>Type: "dev", "optional", or "peer" (can be set multiple times)</li> 223</ul> 224<p>Dependency types to omit from the installation tree on disk.</p> 225<p>Note that these dependencies <em>are</em> still resolved and added to the 226<code>package-lock.json</code> or <code>npm-shrinkwrap.json</code> file. They are just not 227physically installed on disk.</p> 228<p>If a package type appears in both the <code>--include</code> and <code>--omit</code> lists, then 229it will be included.</p> 230<p>If the resulting omit list includes <code>'dev'</code>, then the <code>NODE_ENV</code> environment 231variable will be set to <code>'production'</code> for all lifecycle scripts.</p> 232<h4 id="strict-peer-deps"><code>strict-peer-deps</code></h4> 233<ul> 234<li>Default: false</li> 235<li>Type: Boolean</li> 236</ul> 237<p>If set to <code>true</code>, and <code>--legacy-peer-deps</code> is not set, then <em>any</em> 238conflicting <code>peerDependencies</code> will be treated as an install failure, even 239if npm could reasonably guess the appropriate resolution based on non-peer 240dependency relationships.</p> 241<p>By default, conflicting <code>peerDependencies</code> deep in the dependency graph will 242be resolved using the nearest non-peer dependency specification, even if 243doing so will result in some packages receiving a peer dependency outside 244the range set in their package's <code>peerDependencies</code> object.</p> 245<p>When such an override is performed, a warning is printed, explaining the 246conflict and the packages involved. If <code>--strict-peer-deps</code> is set, then 247this warning is treated as a failure.</p> 248<h4 id="prefer-dedupe"><code>prefer-dedupe</code></h4> 249<ul> 250<li>Default: false</li> 251<li>Type: Boolean</li> 252</ul> 253<p>Prefer to deduplicate packages if possible, rather than choosing a newer 254version of a dependency.</p> 255<h4 id="package-lock"><code>package-lock</code></h4> 256<ul> 257<li>Default: true</li> 258<li>Type: Boolean</li> 259</ul> 260<p>If set to false, then ignore <code>package-lock.json</code> files when installing. This 261will also prevent <em>writing</em> <code>package-lock.json</code> if <code>save</code> is true.</p> 262<h4 id="package-lock-only"><code>package-lock-only</code></h4> 263<ul> 264<li>Default: false</li> 265<li>Type: Boolean</li> 266</ul> 267<p>If set to true, the current operation will only use the <code>package-lock.json</code>, 268ignoring <code>node_modules</code>.</p> 269<p>For <code>update</code> this means only the <code>package-lock.json</code> will be updated, 270instead of checking <code>node_modules</code> and downloading dependencies.</p> 271<p>For <code>list</code> this means the output will be based on the tree described by the 272<code>package-lock.json</code>, rather than the contents of <code>node_modules</code>.</p> 273<h4 id="foreground-scripts"><code>foreground-scripts</code></h4> 274<ul> 275<li>Default: false</li> 276<li>Type: Boolean</li> 277</ul> 278<p>Run all build scripts (ie, <code>preinstall</code>, <code>install</code>, and <code>postinstall</code>) 279scripts for installed packages in the foreground process, sharing standard 280input, output, and error with the main npm process.</p> 281<p>Note that this will generally make installs run slower, and be much noisier, 282but can be useful for debugging.</p> 283<h4 id="ignore-scripts"><code>ignore-scripts</code></h4> 284<ul> 285<li>Default: false</li> 286<li>Type: Boolean</li> 287</ul> 288<p>If true, npm does not run scripts specified in package.json files.</p> 289<p>Note that commands explicitly intended to run a particular script, such as 290<code>npm start</code>, <code>npm stop</code>, <code>npm restart</code>, <code>npm test</code>, and <code>npm run-script</code> 291will still run their intended script if <code>ignore-scripts</code> is set, but they 292will <em>not</em> run any pre- or post-scripts.</p> 293<h4 id="audit"><code>audit</code></h4> 294<ul> 295<li>Default: true</li> 296<li>Type: Boolean</li> 297</ul> 298<p>When "true" submit audit reports alongside the current npm command to the 299default registry and all registries configured for scopes. See the 300documentation for <a href="../commands/npm-audit.html"><code>npm audit</code></a> for details on what is 301submitted.</p> 302<h4 id="bin-links"><code>bin-links</code></h4> 303<ul> 304<li>Default: true</li> 305<li>Type: Boolean</li> 306</ul> 307<p>Tells npm to create symlinks (or <code>.cmd</code> shims on Windows) for package 308executables.</p> 309<p>Set to false to have it not do this. This can be used to work around the 310fact that some file systems don't support symlinks, even on ostensibly Unix 311systems.</p> 312<h4 id="fund"><code>fund</code></h4> 313<ul> 314<li>Default: true</li> 315<li>Type: Boolean</li> 316</ul> 317<p>When "true" displays the message at the end of each <code>npm install</code> 318acknowledging the number of dependencies looking for funding. See <a href="../commands/npm-fund.html"><code>npm fund</code></a> for details.</p> 319<h4 id="dry-run"><code>dry-run</code></h4> 320<ul> 321<li>Default: false</li> 322<li>Type: Boolean</li> 323</ul> 324<p>Indicates that you don't want npm to make any changes and that it should 325only report what it would have done. This can be passed into any of the 326commands that modify your local installation, eg, <code>install</code>, <code>update</code>, 327<code>dedupe</code>, <code>uninstall</code>, as well as <code>pack</code> and <code>publish</code>.</p> 328<p>Note: This is NOT honored by other network related commands, eg <code>dist-tags</code>, 329<code>owner</code>, etc.</p> 330<h4 id="workspace"><code>workspace</code></h4> 331<ul> 332<li>Default:</li> 333<li>Type: String (can be set multiple times)</li> 334</ul> 335<p>Enable running a command in the context of the configured workspaces of the 336current project while filtering by running only the workspaces defined by 337this configuration option.</p> 338<p>Valid values for the <code>workspace</code> config are either:</p> 339<ul> 340<li>Workspace names</li> 341<li>Path to a workspace directory</li> 342<li>Path to a parent workspace directory (will result in selecting all 343workspaces within that folder)</li> 344</ul> 345<p>When set for the <code>npm init</code> command, this may be set to the folder of a 346workspace which does not yet exist, to create the folder and set it up as a 347brand new workspace within the project.</p> 348<p>This value is not exported to the environment for child processes.</p> 349<h4 id="workspaces"><code>workspaces</code></h4> 350<ul> 351<li>Default: null</li> 352<li>Type: null or Boolean</li> 353</ul> 354<p>Set to true to run the command in the context of <strong>all</strong> configured 355workspaces.</p> 356<p>Explicitly setting this to false will cause commands like <code>install</code> to 357ignore workspaces altogether. When not set explicitly:</p> 358<ul> 359<li>Commands that operate on the <code>node_modules</code> tree (install, update, etc.) 360will link workspaces into the <code>node_modules</code> folder. - Commands that do 361other things (test, exec, publish, etc.) will operate on the root project, 362<em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> 363</ul> 364<p>This value is not exported to the environment for child processes.</p> 365<h4 id="include-workspace-root"><code>include-workspace-root</code></h4> 366<ul> 367<li>Default: false</li> 368<li>Type: Boolean</li> 369</ul> 370<p>Include the workspace root when workspaces are enabled for a command.</p> 371<p>When false, specifying individual workspaces via the <code>workspace</code> config, or 372all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on 373the specified workspaces, and not on the root project.</p> 374<p>This value is not exported to the environment for child processes.</p> 375<h4 id="install-links"><code>install-links</code></h4> 376<ul> 377<li>Default: false</li> 378<li>Type: Boolean</li> 379</ul> 380<p>When set file: protocol dependencies will be packed and installed as regular 381dependencies instead of creating a symlink. This option has no effect on 382workspaces.</p> 383<h3 id="see-also">See Also</h3> 384<ul> 385<li><a href="../commands/npm-install.html">npm install</a></li> 386<li><a href="../commands/npm-install-ci-test.html">npm install-ci-test</a></li> 387<li><a href="../commands/npm-test.html">npm test</a></li> 388</ul></div> 389 390<footer id="edit"> 391<a href="https://github.com/npm/cli/edit/latest/docs/content/commands/npm-install-test.md"> 392<svg role="img" viewBox="0 0 16 16" width="16" height="16" fill="currentcolor" style="vertical-align: text-bottom; margin-right: 0.3em;"> 393<path fill-rule="evenodd" d="M11.013 1.427a1.75 1.75 0 012.474 0l1.086 1.086a1.75 1.75 0 010 2.474l-8.61 8.61c-.21.21-.47.364-.756.445l-3.251.93a.75.75 0 01-.927-.928l.929-3.25a1.75 1.75 0 01.445-.758l8.61-8.61zm1.414 1.06a.25.25 0 00-.354 0L10.811 3.75l1.439 1.44 1.263-1.263a.25.25 0 000-.354l-1.086-1.086zM11.189 6.25L9.75 4.81l-6.286 6.287a.25.25 0 00-.064.108l-.558 1.953 1.953-.558a.249.249 0 00.108-.064l6.286-6.286z"></path> 394</svg> 395Edit this page on GitHub 396</a> 397</footer> 398</section> 399 400 401 402</body></html>