[BUG] Docs: Missing info about `access` flag on `npm publish`

[lobsterkatie]

What / Why

Because the only way to turn a public package private (or vice versa) is to use npm access, using (or not using) the --access flag on the npm publish command (after the very first time a package is published) has no effect. It would be nice to note that on the publish docs page (and also here and here). Conversely, it also might be nice to note here that the way to originally set the visibility of a package is with npm publish --access.

When

n/a

Where

The pages linked in the description.

How

Current Behavior

No information about why the publish default (making a package private) doesn't apply after the first time a package is published.

Steps to Reproduce

n/a

Expected Behavior

Information included on page(s).

Who

n/a

References

n/a

[darcyclarke]

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is reproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.

[lobsterkatie]

@darcyclarke This is a docs issue, and it remains in the v7 docs. Any chance of moving this to the V7 category? I will refile if I have to, but I will literally just be copying and pasting.

UPDATE: Thanks, @ljharb!