@cryptotaxi247 / documentation-1
Code Commits Issues Pulls Sessions CI/CD
reggi/cache-based-on-version
@reggi/path-to-regexp dependabot/npm_and_yarn/main/copy-to-clipboard-4.0.2 dependabot/npm_and_yarn/main/eslint-10.4.0 dependabot/npm_and_yarn/main/npmcli/eslint-config-7.0.0 dependabot/npm_and_yarn/main/proc-log-7.0.0 dependabot/npm_and_yarn/npm_and_yarn-826852524d dependabot/npm_and_yarn/npm_and_yarn-ab9a7f4bc2 deprecate-totp-2fa dhei/classic-tokens gat-bypass-2fa-docs jpg619/fix-accessibility-content-flow jpg619/version-bump-tar-2 kartykp/gat-bypass-2fa-docs kartykp/upgrade-path-to-regex main maitxn/version-bump-tar patch-1 reggi/cache-based-on-version reggi/dev-engines reggi/fix-transform-prettier reggi/overrides update-search-sensitivity
mdx 609 lines 25 KB
Raw
1 ---
2 title: npm-install
3 section: 1
4 description: Install a package
5 github_repo: npm/cli
6 github_branch: latest
7 github_path: docs/lib/content/commands/npm-install.md
8 redirect_from:
9 - /cli-commands/install
10 - /cli-commands/npm-install
11 - /cli-documentation/cli-commands/install
12 - /cli-documentation/cli-commands/npm-install
13 - /cli-documentation/commands/install
14 - /cli-documentation/commands/npm-install
15 - /cli-documentation/install
16 - /cli-documentation/npm-install
17 - /cli-documentation/v11/cli-commands/install
18 - /cli-documentation/v11/cli-commands/npm-install
19 - /cli-documentation/v11/commands/install
20 - /cli-documentation/v11/commands/npm-install
21 - /cli-documentation/v11/install
22 - /cli-documentation/v11/npm-install
23 - /cli/cli-commands/install
24 - /cli/cli-commands/npm-install
25 - /cli/commands/install
26 - /cli/commands/npm-install
27 - /cli/install
28 - /cli/npm-install
29 - /cli/v11/cli-commands/install
30 - /cli/v11/cli-commands/npm-install
31 - /cli/v11/commands/install
32 - /cli/v11/install
33 - /cli/v11/npm-install
34 - /commands/install
35 - /commands/npm-install
36 ---
37
38 ### Synopsis
39
40 ```bash
41 npm install [<package-spec> ...]
42
43 aliases: add, i, in, ins, inst, insta, instal, isnt, isnta, isntal, isntall
44 ```
45
46 ### Description
47
48 This command installs a package and any packages that it depends on. If the package has a package-lock, or an npm shrinkwrap file, or a yarn lock file, the installation of dependencies will be driven by that, respecting the following order of precedence:
49
50 - `npm-shrinkwrap.json`
51 - `package-lock.json`
52 - `yarn.lock`
53
54 See [package-lock.json](/cli/v11/configuring-npm/package-lock-json) and [`npm shrinkwrap`](/cli/v11/commands/npm-shrinkwrap).
55
56 A `package` is:
57
58 - a) a folder containing a program described by a [`package.json`](/cli/v11/configuring-npm/package-json) file
59 - b) a gzipped tarball containing (a)
60 - c) a url that resolves to (b)
61 - d) a `<name>@<version>` that is published on the registry (see [`registry`](/cli/v11/using-npm/registry)) with (c)
62 - e) a `<name>@<tag>` (see [`npm dist-tag`](/cli/v11/commands/npm-dist-tag)) that points to (d)
63 - f) a `<name>` that has a "latest" tag satisfying (e)
64 - g) a `<git remote url>` that resolves to (a)
65
66 Even if you never publish your package, you can still get a lot of benefits of using npm if you just want to write a node program (a), and perhaps if you also want to be able to easily install it elsewhere after packing it up into a tarball (b).
67
68 - `npm install` (in a package directory, no arguments):
69
70 Install the dependencies to the local `node_modules` folder.
71
72 In global mode (ie, with `-g` or `--global` appended to the command), it installs the current package context (ie, the current working directory) as a global package.
73
74 By default, `npm install` will install all modules listed as dependencies in [`package.json`](/cli/v11/configuring-npm/package-json).
75
76 With the `--production` flag (or when the `NODE_ENV` environment variable is set to `production`), npm will not install modules listed in `devDependencies`. To install all modules listed in both `dependencies` and `devDependencies` when `NODE_ENV` environment variable is set to `production`, you can use `--production=false`.
77
78 > NOTE: The `--production` flag has no particular meaning when adding a dependency to a project.
79
80 - `npm install <folder>`:
81
82 If `<folder>` sits inside the root of your project, its dependencies will be installed and may be hoisted to the top-level `node_modules` as they would for other types of dependencies. If `<folder>` sits outside the root of your project, _npm will not install the package dependencies_ in the directory `<folder>`, but it will create a symlink to `<folder>`.
83
84 > NOTE: If you want to install the content of a directory like a package from the registry instead of creating a link, you would need to use the `--install-links` option.
85
86 Example:
87
88 ```bash
89 npm install ../../other-package --install-links
90 npm install ./sub-package
91 ```
92
93 - `npm install <tarball file>`:
94
95 Install a package that is sitting on the filesystem. Note: if you just want to link a dev directory into your npm root, you can do this more easily by using [`npm link`](/cli/v11/commands/npm-link).
96
97 Tarball requirements:
98
99 - The filename _must_ use `.tar`, `.tar.gz`, or `.tgz` as the extension.
100 - The package contents should reside in a subfolder inside the tarball (usually it is called `package/`). npm strips one directory layer when installing the package (an equivalent of `tar x --strip-components=1` is run).
101 - The package must contain a `package.json` file with `name` and `version` properties.
102
103 Example:
104
105 ```bash
106 npm install ./package.tgz
107 ```
108
109 - `npm install <tarball url>`:
110
111 Fetch the tarball url, and then install it. In order to distinguish between this and other options, the argument must start with "http://" or "https://"
112
113 Example:
114
115 ```bash
116 npm install https://github.com/indexzero/forever/tarball/v0.5.6
117 ```
118
119 - `npm install [<@scope>/]<name>`:
120
121 Do a `<name>@<tag>` install, where `<tag>` is the "tag" config. (See [`config`](/cli/v11/using-npm/config#tag). The config's default value is `latest`.)
122
123 In most cases, this will install the version of the modules tagged as `latest` on the npm registry.
124
125 Example:
126
127 ```bash
128 npm install sax
129 ```
130
131 `npm install` saves any specified packages into `dependencies` by default. Additionally, you can control where and how they get saved with some additional flags:
132
133 - `-P, --save-prod`: Package will appear in your `dependencies`. This is the default unless `-D` or `-O` are present.
134
135 - `-D, --save-dev`: Package will appear in your `devDependencies`.
136
137 - `--save-peer`: Package will appear in your `peerDependencies`.
138
139 - `-O, --save-optional`: Package will appear in your `optionalDependencies`.
140
141 - `--no-save`: Prevents saving to `dependencies`.
142
143 When using any of the above options to save dependencies to your package.json, there are two additional, optional flags:
144
145 - `-E, --save-exact`: Saved dependencies will be configured with an exact version rather than using npm's default semver range operator.
146
147 - `-B, --save-bundle`: Saved dependencies will also be added to your `bundleDependencies` list.
148
149 Further, if you have an `npm-shrinkwrap.json` or `package-lock.json` then it will be updated as well.
150
151 `<scope>` is optional. The package will be downloaded from the registry associated with the specified scope. If no registry is associated with the given scope the default registry is assumed. See [`scope`](/cli/v11/using-npm/scope).
152
153 Note: if you do not include the @-symbol on your scope name, npm will interpret this as a GitHub repository instead, see below. Scopes names must also be followed by a slash.
154
155 Examples:
156
157 ```bash
158 npm install sax
159 npm install githubname/reponame
160 npm install @myorg/privatepackage
161 npm install node-tap --save-dev
162 npm install dtrace-provider --save-optional
163 npm install readable-stream --save-exact
164 npm install ansi-regex --save-bundle
165 ```
166
167 - `npm install <alias>@npm:<name>`:
168
169 Install a package under a custom alias. Allows multiple versions of a same-name package side-by-side, more convenient import names for packages with otherwise long ones, and using git forks replacements or forked npm packages as replacements. Aliasing works only on your project and does not rename packages in transitive dependencies. Aliases should follow the naming conventions stated in [`validate-npm-package-name`](https://www.npmjs.com/package/validate-npm-package-name#naming-rules).
170
171 Examples:
172
173 ```bash
174 npm install my-react@npm:react
175 npm install jquery2@npm:jquery@2
176 npm install jquery3@npm:jquery@3
177 npm install npa@npm:npm-package-arg
178 ```
179
180 - `npm install [<@scope>/]<name>@<tag>`:
181
182 Install the version of the package that is referenced by the specified tag. If the tag does not exist in the registry data for that package, then this will fail.
183
184 Example:
185
186 ```bash
187 npm install sax@latest
188 npm install @myorg/mypackage@latest
189 ```
190
191 - `npm install [<@scope>/]<name>@<version>`:
192
193 Install the specified version of the package. This will fail if the version has not been published to the registry.
194
195 Example:
196
197 ```bash
198 npm install sax@0.1.1
199 npm install @myorg/privatepackage@1.5.0
200 ```
201
202 - `npm install [<@scope>/]<name>@<version range>`:
203
204 Install a version of the package matching the specified version range. This will follow the same rules for resolving dependencies described in [`package.json`](/cli/v11/configuring-npm/package-json).
205
206 Note that most version ranges must be put in quotes so that your shell will treat it as a single argument.
207
208 Example:
209
210 ```bash
211 npm install sax@">=0.1.0 <0.2.0"
212 npm install @myorg/privatepackage@"16 - 17"
213 ```
214
215 - `npm install <git remote url>`:
216
217 Installs the package from the hosted git provider, cloning it with `git`. For a full git remote url, only that URL will be attempted.
218
219 ```bash
220 <protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>[#<commit-ish> | #semver:<semver>]
221 ```
222
223 `<protocol>` is one of `git`, `git+ssh`, `git+http`, `git+https`, or `git+file`.
224
225 If `#<commit-ish>` is provided, it will be used to clone exactly that commit. If the commit-ish has the format `#semver:<semver>`, `<semver>` can be any valid semver range or exact version, and npm will look for any tags or refs matching that range in the remote repository, much as it would for a registry dependency. If neither `#<commit-ish>` or `#semver:<semver>` is specified, then the default branch of the repository is used.
226
227 If the repository makes use of submodules, those submodules will be cloned as well.
228
229 If the package being installed contains a `prepare` script, its `dependencies` and `devDependencies` will be installed, and the prepare script will be run, before the package is packaged and installed.
230
231 The following git environment variables are recognized by npm and will be added to the environment when running git:
232
233 - `GIT_ASKPASS`
234 - `GIT_EXEC_PATH`
235 - `GIT_PROXY_COMMAND`
236 - `GIT_SSH`
237 - `GIT_SSH_COMMAND`
238 - `GIT_SSL_CAINFO`
239 - `GIT_SSL_NO_VERIFY`
240
241 See the git man page for details.
242
243 Examples:
244
245 ```bash
246 npm install git+ssh://git@github.com:npm/cli.git#v1.0.27
247 npm install git+ssh://git@github.com:npm/cli#pull/273
248 npm install git+ssh://git@github.com:npm/cli#semver:^5.0
249 npm install git+https://isaacs@github.com/npm/cli.git
250 npm install git://github.com/npm/cli.git#v1.0.27
251 GIT_SSH_COMMAND='ssh -i ~/.ssh/custom_ident' npm install git+ssh://git@github.com:npm/cli.git
252 ```
253
254 - `npm install <githubname>/<githubrepo>[#<commit-ish>]`:
255 - `npm install github:<githubname>/<githubrepo>[#<commit-ish>]`:
256
257 Install the package at `https://github.com/githubname/githubrepo` by attempting to clone it using `git`.
258
259 If `#<commit-ish>` is provided, it will be used to clone exactly that commit. If the commit-ish has the format `#semver:<semver>`, `<semver>` can be any valid semver range or exact version, and npm will look for any tags or refs matching that range in the remote repository, much as it would for a registry dependency. If neither `#<commit-ish>` or `#semver:<semver>` is specified, then the default branch is used.
260
261 As with regular git dependencies, `dependencies` and `devDependencies` will be installed if the package has a `prepare` script before the package is done installing.
262
263 Examples:
264
265 ```bash
266 npm install mygithubuser/myproject
267 npm install github:mygithubuser/myproject
268 ```
269
270 - `npm install gist:[<githubname>/]<gistID>[#<commit-ish>|#semver:<semver>]`:
271
272 Install the package at `https://gist.github.com/gistID` by attempting to clone it using `git`. The GitHub username associated with the gist is optional and will not be saved in `package.json`.
273
274 As with regular git dependencies, `dependencies` and `devDependencies` will be installed if the package has a `prepare` script before the package is done installing.
275
276 Example:
277
278 ```bash
279 npm install gist:101a11beef
280 ```
281
282 - `npm install bitbucket:<bitbucketname>/<bitbucketrepo>[#<commit-ish>]`:
283
284 Install the package at `https://bitbucket.org/bitbucketname/bitbucketrepo` by attempting to clone it using `git`.
285
286 If `#<commit-ish>` is provided, it will be used to clone exactly that commit. If the commit-ish has the format `#semver:<semver>`, `<semver>` can be any valid semver range or exact version, and npm will look for any tags or refs matching that range in the remote repository, much as it would for a registry dependency. If neither `#<commit-ish>` or `#semver:<semver>` is specified, then `master` is used.
287
288 As with regular git dependencies, `dependencies` and `devDependencies` will be installed if the package has a `prepare` script before the package is done installing.
289
290 Example:
291
292 ```bash
293 npm install bitbucket:mybitbucketuser/myproject
294 ```
295
296 - `npm install gitlab:<gitlabname>/<gitlabrepo>[#<commit-ish>]`:
297
298 Install the package at `https://gitlab.com/gitlabname/gitlabrepo` by attempting to clone it using `git`.
299
300 If `#<commit-ish>` is provided, it will be used to clone exactly that commit. If the commit-ish has the format `#semver:<semver>`, `<semver>` can be any valid semver range or exact version, and npm will look for any tags or refs matching that range in the remote repository, much as it would for a registry dependency. If neither `#<commit-ish>` or `#semver:<semver>` is specified, then `master` is used.
301
302 As with regular git dependencies, `dependencies` and `devDependencies` will be installed if the package has a `prepare` script before the package is done installing.
303
304 Example:
305
306 ```bash
307 npm install gitlab:mygitlabuser/myproject
308 npm install gitlab:myusr/myproj#semver:^5.0
309 ```
310
311 You may combine multiple arguments and even multiple types of arguments. For example:
312
313 ```bash
314 npm install sax@">=0.1.0 <0.2.0" bench supervisor
315 ```
316
317 The `--tag` argument will apply to all of the specified install targets. If a tag with the given name exists, the tagged version is preferred over newer versions.
318
319 The `--dry-run` argument will report in the usual way what the install would have done without actually installing anything.
320
321 The `--package-lock-only` argument will only update the `package-lock.json`, instead of checking `node_modules` and downloading dependencies.
322
323 The `-f` or `--force` argument will force npm to fetch remote resources even if a local copy exists on disk.
324
325 ```bash
326 npm install sax --force
327 ```
328
329 ### Configuration
330
331 See the [`config`](/cli/v11/using-npm/config) help doc. Many of the configuration params have some effect on installation, since that's most of what npm does.
332
333 These are some of the most common options related to installation.
334
335 #### `save`
336
337 - Default: `true` unless when using `npm update` where it defaults to `false`
338 - Type: Boolean
339
340 Save installed packages to a `package.json` file as dependencies.
341
342 When used with the `npm rm` command, removes the dependency from `package.json`.
343
344 Will also prevent writing to `package-lock.json` if set to `false`.
345
346 #### `save-exact`
347
348 - Default: false
349 - Type: Boolean
350
351 Dependencies saved to package.json will be configured with an exact version rather than using npm's default semver range operator.
352
353 #### `global`
354
355 - Default: false
356 - Type: Boolean
357
358 Operates in "global" mode, so that packages are installed into the `prefix` folder instead of the current working directory. See [folders](/cli/v11/configuring-npm/folders) for more on the differences in behavior.
359
360 - packages are installed into the `{prefix}/lib/node_modules` folder, instead of the current working directory.
361 - bin files are linked to `{prefix}/bin`
362 - man pages are linked to `{prefix}/share/man`
363
364 #### `install-strategy`
365
366 - Default: "hoisted"
367 - Type: "hoisted", "nested", "shallow", or "linked"
368
369 Sets the strategy for installing packages in node_modules. hoisted (default): Install non-duplicated in top-level, and duplicated as necessary within directory structure. nested: (formerly --legacy-bundling) install in place, no hoisting. shallow (formerly --global-style) only install direct deps at top-level. linked: (experimental) install in node_modules/.store, link in place, unhoisted.
370
371 #### `legacy-bundling`
372
373 - Default: false
374 - Type: Boolean
375 - DEPRECATED: This option has been deprecated in favor of `--install-strategy=nested`
376
377 Instead of hoisting package installs in `node_modules`, install packages in the same manner that they are depended on. This may cause very deep directory structures and duplicate package installs as there is no de-duplicating. Sets `--install-strategy=nested`.
378
379 #### `global-style`
380
381 - Default: false
382 - Type: Boolean
383 - DEPRECATED: This option has been deprecated in favor of `--install-strategy=shallow`
384
385 Only install direct dependencies in the top level `node_modules`, but hoist on deeper dependencies. Sets `--install-strategy=shallow`.
386
387 #### `omit`
388
389 - Default: 'dev' if the `NODE_ENV` environment variable is set to 'production', otherwise empty.
390 - Type: "dev", "optional", or "peer" (can be set multiple times)
391
392 Dependency types to omit from the installation tree on disk.
393
394 Note that these dependencies _are_ still resolved and added to the `package-lock.json` or `npm-shrinkwrap.json` file. They are just not physically installed on disk.
395
396 If a package type appears in both the `--include` and `--omit` lists, then it will be included.
397
398 If the resulting omit list includes `'dev'`, then the `NODE_ENV` environment variable will be set to `'production'` for all lifecycle scripts.
399
400 #### `include`
401
402 - Default:
403 - Type: "prod", "dev", "optional", or "peer" (can be set multiple times)
404
405 Option that allows for defining which types of dependencies to install.
406
407 This is the inverse of `--omit=<type>`.
408
409 Dependency types specified in `--include` will not be omitted, regardless of the order in which omit/include are specified on the command-line.
410
411 #### `strict-peer-deps`
412
413 - Default: false
414 - Type: Boolean
415
416 If set to `true`, and `--legacy-peer-deps` is not set, then _any_ conflicting `peerDependencies` will be treated as an install failure, even if npm could reasonably guess the appropriate resolution based on non-peer dependency relationships.
417
418 By default, conflicting `peerDependencies` deep in the dependency graph will be resolved using the nearest non-peer dependency specification, even if doing so will result in some packages receiving a peer dependency outside the range set in their package's `peerDependencies` object.
419
420 When such an override is performed, a warning is printed, explaining the conflict and the packages involved. If `--strict-peer-deps` is set, then this warning is treated as a failure.
421
422 #### `prefer-dedupe`
423
424 - Default: false
425 - Type: Boolean
426
427 Prefer to deduplicate packages if possible, rather than choosing a newer version of a dependency.
428
429 #### `package-lock`
430
431 - Default: true
432 - Type: Boolean
433
434 If set to false, then ignore `package-lock.json` files when installing. This will also prevent _writing_ `package-lock.json` if `save` is true.
435
436 #### `package-lock-only`
437
438 - Default: false
439 - Type: Boolean
440
441 If set to true, the current operation will only use the `package-lock.json`, ignoring `node_modules`.
442
443 For `update` this means only the `package-lock.json` will be updated, instead of checking `node_modules` and downloading dependencies.
444
445 For `list` this means the output will be based on the tree described by the `package-lock.json`, rather than the contents of `node_modules`.
446
447 #### `foreground-scripts`
448
449 - Default: `false` unless when using `npm pack` or `npm publish` where it defaults to `true`
450 - Type: Boolean
451
452 Run all build scripts (ie, `preinstall`, `install`, and `postinstall`) scripts for installed packages in the foreground process, sharing standard input, output, and error with the main npm process.
453
454 Note that this will generally make installs run slower, and be much noisier, but can be useful for debugging.
455
456 #### `ignore-scripts`
457
458 - Default: false
459 - Type: Boolean
460
461 If true, npm does not run scripts specified in package.json files.
462
463 Note that commands explicitly intended to run a particular script, such as `npm start`, `npm stop`, `npm restart`, `npm test`, and `npm run-script` will still run their intended script if `ignore-scripts` is set, but they will _not_ run any pre- or post-scripts.
464
465 #### `audit`
466
467 - Default: true
468 - Type: Boolean
469
470 When "true" submit audit reports alongside the current npm command to the default registry and all registries configured for scopes. See the documentation for [`npm audit`](/cli/v11/commands/npm-audit) for details on what is submitted.
471
472 #### `bin-links`
473
474 - Default: true
475 - Type: Boolean
476
477 Tells npm to create symlinks (or `.cmd` shims on Windows) for package executables.
478
479 Set to false to have it not do this. This can be used to work around the fact that some file systems don't support symlinks, even on ostensibly Unix systems.
480
481 #### `fund`
482
483 - Default: true
484 - Type: Boolean
485
486 When "true" displays the message at the end of each `npm install` acknowledging the number of dependencies looking for funding. See [`npm fund`](/cli/v11/commands/npm-fund) for details.
487
488 #### `dry-run`
489
490 - Default: false
491 - Type: Boolean
492
493 Indicates that you don't want npm to make any changes and that it should only report what it would have done. This can be passed into any of the commands that modify your local installation, eg, `install`, `update`, `dedupe`, `uninstall`, as well as `pack` and `publish`.
494
495 Note: This is NOT honored by other network related commands, eg `dist-tags`, `owner`, etc.
496
497 #### `cpu`
498
499 - Default: null
500 - Type: null or String
501
502 Override CPU architecture of native modules to install. Acceptable values are same as `cpu` field of package.json, which comes from `process.arch`.
503
504 #### `os`
505
506 - Default: null
507 - Type: null or String
508
509 Override OS of native modules to install. Acceptable values are same as `os` field of package.json, which comes from `process.platform`.
510
511 #### `libc`
512
513 - Default: null
514 - Type: null or String
515
516 Override libc of native modules to install. Acceptable values are same as `libc` field of package.json
517
518 #### `workspace`
519
520 - Default:
521 - Type: String (can be set multiple times)
522
523 Enable running a command in the context of the configured workspaces of the current project while filtering by running only the workspaces defined by this configuration option.
524
525 Valid values for the `workspace` config are either:
526
527 - Workspace names
528 - Path to a workspace directory
529 - Path to a parent workspace directory (will result in selecting all workspaces within that folder)
530
531 When set for the `npm init` command, this may be set to the folder of a workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.
532
533 This value is not exported to the environment for child processes.
534
535 #### `workspaces`
536
537 - Default: null
538 - Type: null or Boolean
539
540 Set to true to run the command in the context of **all** configured workspaces.
541
542 Explicitly setting this to false will cause commands like `install` to ignore workspaces altogether. When not set explicitly:
543
544 - Commands that operate on the `node_modules` tree (install, update, etc.) will link workspaces into the `node_modules` folder. - Commands that do other things (test, exec, publish, etc.) will operate on the root project, _unless_ one or more workspaces are specified in the `workspace` config.
545
546 This value is not exported to the environment for child processes.
547
548 #### `include-workspace-root`
549
550 - Default: false
551 - Type: Boolean
552
553 Include the workspace root when workspaces are enabled for a command.
554
555 When false, specifying individual workspaces via the `workspace` config, or all workspaces via the `workspaces` flag, will cause npm to operate only on the specified workspaces, and not on the root project.
556
557 This value is not exported to the environment for child processes.
558
559 #### `install-links`
560
561 - Default: false
562 - Type: Boolean
563
564 When set file: protocol dependencies will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces.
565
566 ### Algorithm
567
568 Given a `package{dep}` structure: `A{B,C}, B{C}, C{D}`, the npm install algorithm produces:
569
570 ```bash
571 A
572 +-- B
573 +-- C
574 +-- D
575 ```
576
577 That is, the dependency from B to C is satisfied by the fact that A already caused C to be installed at a higher level. D is still installed at the top level because nothing conflicts with it.
578
579 For `A{B,C}, B{C,D@1}, C{D@2}`, this algorithm produces:
580
581 ```bash
582 A
583 +-- B
584 +-- C
585 `-- D@2
586 +-- D@1
587 ```
588
589 Because B's D@1 will be installed in the top-level, C now has to install D@2 privately for itself. This algorithm is deterministic, but different trees may be produced if two dependencies are requested for installation in a different order.
590
591 See [folders](/cli/v11/configuring-npm/folders) for a more detailed description of the specific folder structures that npm creates.
592
593 ### See Also
594
595 - [npm folders](/cli/v11/configuring-npm/folders)
596 - [npm update](/cli/v11/commands/npm-update)
597 - [npm audit](/cli/v11/commands/npm-audit)
598 - [npm fund](/cli/v11/commands/npm-fund)
599 - [npm link](/cli/v11/commands/npm-link)
600 - [npm rebuild](/cli/v11/commands/npm-rebuild)
601 - [npm scripts](/cli/v11/using-npm/scripts)
602 - [npm config](/cli/v11/commands/npm-config)
603 - [npmrc](/cli/v11/configuring-npm/npmrc)
604 - [npm registry](/cli/v11/using-npm/registry)
605 - [npm dist-tag](/cli/v11/commands/npm-dist-tag)
606 - [npm uninstall](/cli/v11/commands/npm-uninstall)
607 - [npm shrinkwrap](/cli/v11/commands/npm-shrinkwrap)
608 - [package.json](/cli/v11/configuring-npm/package-json)
609 - [workspaces](/cli/v11/using-npm/workspaces)