CLI documentation update from CI
CI User committed
Sep 24, 2021 at 02:26 UTC
8e884bc33903a7fbc7c70173472cfe2c0ea5ce7a
3 files changed
+12
-3
cli/v7
+1
-1
@@ -1 +1 @@
1
-Subproject commit 2c741900f560fd3ad0d5fa8afe583fbd83c5dbbe
1
+Subproject commit 6ae8cbe7ed70c17b121bd9ea42f8d8af11823c18
content/cli/v7/configuring-npm/package-lock-json.md
+4
-2
@@ -146,7 +146,8 @@ Package descriptors have the following fields:
146
the case of packages fetched from the registry, this will be a url to a
147
tarball. In the case of git dependencies, this will be the full git url
148
with commit sha. In the case of link dependencies, this will be the
149
- location of the link target.
149
+ location of the link target. `registry.npmjs.org` is a magic value meaning
150
+ "the currently configured registry".
151
152
* integrity: A `sha512` or `sha1` [Standard Subresource
153
Integrity](https://w3c.github.io/webappsec/specs/subresourceintegrity/)
@@ -209,7 +210,8 @@ Dependency objects have the following fields:
210
211
* resolved: For registry sources this is path of the tarball relative to
212
the registry URL. If the tarball URL isn't on the same server as the
212
- registry URL then this is a complete URL.
213
+ registry URL then this is a complete URL. `registry.npmjs.org` is a magic
214
+ value meaning "the currently configured registry".
215
216
* bundled: If true, this is the bundled dependency and will be installed
217
by the parent module. When installing, this module will be extracted
content/cli/v7/using-npm/registry.md
+7
@@ -38,6 +38,13 @@ The registry URL used is determined by the scope of the package (see
38
supplied by the `registry` config parameter. See [`npm config`](/cli/v7/commands/npm-config),
39
[`npmrc`](/cli/v7/configuring-npm/npmrc), and [`config`](/cli/v7/using-npm/config) for more on managing npm's configuration.
40
41
+When the default registry is used in a package-lock or shrinkwrap is has the
42
+special meaning of "the currently configured registry". If you create a lock
43
+file while using the default registry you can switch to another registry and
44
+npm will install packages from the new registry, but if you create a lock
45
+file while using a custom registry packages will be installed from that
46
+registry even after you change to another registry.
47
+
48
### Does npm send any information about me back to the registry?
49
50
Yes.