CLI documentation update from CI
CI User committed
Feb 17, 2022 at 02:26 UTC
4ec1974c8cc639c868142c4c49901520fd074a23
2 files changed
+14
-5
cli/v8
+1
-1
@@ -1 +1 @@
1
-Subproject commit 20a981890ba96d946036419f0ac124fe598663b7
1
+Subproject commit 20c83fae76ff4a051e4f6542a328f1c00cf071bb
content/cli/v8/commands/npm-install.md
+13
-4
@@ -89,11 +89,20 @@ into a tarball (b).
89
90
* `npm install <folder>`:
91
92
- Install the package in the directory as a symlink in the current
93
- project. Its dependencies will be installed before it's linked. If
94
- `<folder>` sits inside the root of your project, its dependencies may
92
+ If `<folder>` sits inside the root of your project, its dependencies will be installed and may
93
be hoisted to the top-level `node_modules` as they would for other
96
- types of dependencies.
94
+ types of dependencies. If `<folder>` sits outside the root of your project,
95
+ *npm will not install the package dependencies* in the directory `<folder>`,
96
+ but it will create a symlink to `<folder>`.
97
+
98
+ > 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 [`npm pack`](/cli/v8/commands/npm-pack) while in the `<folder>` directory, and then install the resulting tarball instead of the `<folder>` using `npm install <tarball file>`
99
+
100
+ Example:
101
+
102
+ ```bash
103
+ npm install ../../other-package
104
+ npm install ./sub-package
105
+ ```
106
107
* `npm install <tarball file>`:
108