From d1812f1a627d6a4d4cb6d07d7735d2d2cc2cf264 Mon Sep 17 00:00:00 2001 From: austincho Date: Sun, 8 Aug 2021 10:40:52 -0700 Subject: [PATCH] fix(docs): update npm-publish access flag info PR-URL: https://github.com/npm/cli/pull/3630 Credit: @austincho Close: #3630 Reviewed-by: @wraithgar --- docs/content/commands/npm-publish.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/content/commands/npm-publish.md b/docs/content/commands/npm-publish.md index 0d25d7d29da8d..9eb060a78be29 100644 --- a/docs/content/commands/npm-publish.md +++ b/docs/content/commands/npm-publish.md @@ -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`. + #### `dry-run` * Default: false