v7.24.1

AUTHORS

@@ -799,3 +799,4 @@ John Gee <john@ruru.gen.nz>
 Ayush Rawal <royalrawal.2001@gmail.com>
 Nate Green <heynategreen@gmail.com>
 Jacob Yacovelli <jjyacovelli@gmail.com>
+Caleb ツ Everett <calebev@amazon.com>

CHANGELOG.md

@@ -1,3 +1,20 @@
+## v7.24.1 (2021-09-23)
+
+### DEPENDENCIES
+
+* [`1be8d41e6`](https://github.com/npm/cli/commit/1be8d41e6f23f7a3d8411a31099ab546fbcb5bfa)
+  `socks-proxy-agent@6.1.0`:
+  * feat: allow passing tls connection options
+* [`eafd55eae`](https://github.com/npm/cli/commit/eafd55eae219a6c15d2857d06b673a67d7f7d060)
+  `glob@7.2.0`
+
+### DOCS
+
+* [`dae5ce305`](https://github.com/npm/cli/commit/dae5ce3055ded57eab8aa3425004c60224a6fe67)
+  [#3784](https://github.com/npm/cli/issues/3784)
+  docs: document special meaning of registry.npmjs.com
+  ([@everett1992](https://github.com/everett1992))
+
 ## v7.24.0 (2021-09-16)
 
 ### FEATURES

docs/content/configuring-npm/package-lock-json.md

@@ -138,7 +138,8 @@ Package descriptors have the following fields:
   the case of packages fetched from the registry, this will be a url to a
   tarball.  In the case of git dependencies, this will be the full git url
   with commit sha.  In the case of link dependencies, this will be the
-  location of the link target.
+  location of the link target. `registry.npmjs.org` is a magic value meaning
+  "the currently configured registry".
 
 * integrity: A `sha512` or `sha1` [Standard Subresource
   Integrity](https://w3c.github.io/webappsec/specs/subresourceintegrity/)
@@ -201,7 +202,8 @@ Dependency objects have the following fields:
 
 * resolved: For registry sources this is path of the tarball relative to
   the registry URL.  If the tarball URL isn't on the same server as the
-  registry URL then this is a complete URL.
+  registry URL then this is a complete URL. `registry.npmjs.org` is a magic
+  value meaning "the currently configured registry".
 
 * bundled:  If true, this is the bundled dependency and will be installed
   by the parent module.  When installing, this module will be extracted

docs/content/using-npm/registry.md

@@ -30,6 +30,13 @@ The registry URL used is determined by the scope of the package (see
 supplied by the `registry` config parameter.  See [`npm config`](/commands/npm-config),
 [`npmrc`](/configuring-npm/npmrc), and [`config`](/using-npm/config) for more on managing npm's configuration.
 
+When the default registry is used in a package-lock or shrinkwrap is has the
+special meaning of "the currently configured registry". If you create a lock
+file while using the default registry you can switch to another registry and
+npm will install packages from the new registry, but if you create a lock
+file while using a custom registry packages will be installed from that
+registry even after you change to another registry.
+
 ### Does npm send any information about me back to the registry?
 
 Yes.

lib/deprecate.js

@@ -49,7 +49,7 @@ class Deprecate extends BaseCommand {
   }
 
   async deprecate ([pkg, msg]) {
-    // msg == null becase '' is a valid value, it indicates undeprecate
+    // msg == null because '' is a valid value, it indicates undeprecate
     if (!pkg || msg == null)
       throw this.usageError()