CLI documentation update from CI
CI User committed
Apr 22, 2022 at 03:01 UTC
bdcb135ab6ff132bb56f1c3c7233993776164db6
3 files changed
+20
-4
cli/v8
+1
-1
@@ -1 +1 @@
1
-Subproject commit 52fd23bf05d5017b05ba67e1c1a94e2244e91093
1
+Subproject commit fa3d82989df7071cfe500c5f9cc09c597bcc17ee
content/cli/v8/using-npm/config.md
+2
@@ -146,6 +146,8 @@ npm ls --global --parseable --long --loglevel info
146
* Type: null or String
147
148
A basic-auth string to use when authenticating against the npm registry.
149
+This will ONLY be used to authenticate against the npm registry. For other
150
+registries you will need to scope it like "//other-registry.tld/:_auth"
151
152
Warning: This should generally not be set via a command-line option. It is
153
safer to use a registry-provided authentication bearer token stored in the
content/cli/v8/using-npm/scope.md
+17
-3
@@ -88,9 +88,23 @@ If you wish, you may associate a scope with a registry; see below.
88
89
#### Publishing public scoped packages to the primary npm registry
90
91
-To publish a public scoped package, you must specify `--access public` with
92
-the initial publication. This will publish the package and set access
93
-to `public` as if you had run `npm access public` after publishing.
91
+Publishing to a scope, you have two options:
92
+
93
+- Publishing to your user scope (example: `@username/module`)
94
+- Publishing to an organization scope (example: `@org/module`)
95
+
96
+If publishing a public module to an organization scope, you must
97
+first either create an organization with the name of the scope
98
+that you'd like to publish to or be added to an existing organization
99
+with the appropriate permisssions. For example, if you'd like to
100
+publish to `@org`, you would need to create the `org` organization
101
+on npmjs.com prior to trying to publish.
102
+
103
+Scoped packages are not public by default. You will need to specify
104
+`--access public` with the initial `npm publish` command. This will publish
105
+the package and set access to `public` as if you had run `npm access public`
106
+after publishing. You do not need to do this when publishing new versions of
107
+an existing scoped package.
108
109
#### Publishing private scoped packages to the npm registry
110