Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(docs): update npm-publish access flag info #3630

Merged
merged 1 commit into from Aug 11, 2021
+5 −0
Merged

fix(docs): update npm-publish access flag info #3630

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/content/commands/npm-publish.md
View file
Open in desktop
Expand Up @@ -132,6 +132,11 @@ If you want your scoped package to be publicly viewable (and installable)
set `--access=public`. The only valid values for `access` are `public` and
`restricted`. Unscoped packages _always_ have an access level of `public`.

Note: Using the `--access` flag on the `npm publish` command will only set
the package access level on the initial publish of the package. Any subsequent `npm publish`
commands using the `--access` flag will not have an effect to the access level.
To make changes to the access level after the initial publish use `npm access`.

austincho marked this conversation as resolved.
Show resolved Hide resolved
#### `dry-run`

* Default: false
Expand Down