CLI documentation update from CI
npm CLI robot committed
Mar 20, 2025 at 02:40 UTC
9dca3a3d4237a90c943ec746bc6323181cc0e937
2 files changed
+3
-1
cli-cache.json
+1
-1
@@ -2,5 +2,5 @@
2
"v8": "aa8fff11cdab94fff1a2160ee5241f5f4632e96b",
3
"v9": "64763a341e7aa5b456e696f956759bf9b3440dc1",
4
"v10": "a3041941586b6fb8ed7403fe3c24d81138a96005",
5
- "v11": "4183cba3e13bcfea83fa3ef2b6c5b0c9685f79bc"
5
+ "v11": "1642556fe47d837ab7d0800d96bd2eebd0c908fd"
6
}
\ No newline at end of file
content/cli/v11/using-npm/registry.mdx
+2
@@ -27,6 +27,8 @@ You can configure npm to use any compatible registry you like, and even run your
27
28
npm's package registry implementation supports several write APIs as well, to allow for publishing packages and managing user account information.
29
30
+The npm public registry is powered by a CouchDB database, of which there is a public mirror at [https://skimdb.npmjs.com/registry](https://skimdb.npmjs.com/registry).
31
+
32
The registry URL used is determined by the scope of the package (see [`scope`](/cli/v11/using-npm/scope). If no scope is specified, the default registry is used, which is supplied by the [`registry` config](/cli/v11/using-npm/config#registry) parameter. See [`npm config`](/cli/v11/commands/npm-config), [`npmrc`](/cli/v11/configuring-npm/npmrc), and [`config`](/cli/v11/using-npm/config) for more on managing npm's configuration. Authentication configuration such as auth tokens and certificates are configured specifically scoped to an individual registry. See [Auth Related Configuration](/cli/v11/configuring-npm/npmrc#auth-related-configuration)
33
34
When the default registry is used in a package-lock or shrinkwrap it 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.