feat(access): Deprecate & warn for subcommands

[darcyclarke]

Summary

We will be removing a number of npm access commands in v9 (ref. #486); show warnings when someone uses them in v8.x.

Exit Criteria

• start throwing a warning for deprecation of 2fa-required
• start throwing a warning for deprecation of 2fa-not-required
• start throwing a warning for deprecation of public
• start throwing a warning for deprecation of restricted
• start throwing a warning for deprecation of edit
• start throwing a warning for deprecation of ls-packages
• start throwing a warning for deprecation of ls-collaborators

[wraithgar]

edit is not implemented yet so no warning is needed.

  async edit () {
    throw new Error('edit subcommand is not implemented yet')
  }

[wraithgar]

PR implementing this is here, ready for copy editing if needs be npm/cli#5347

[jaswrks]

@wraithgar Hi. Was grant / revoke intended to be a part of this and deprecated? If so, do you know what is going to replace them? I don't see any other functionality in the CLI that's equivalent, and these were not deprecated in the latest release.

[wraithgar]

Those subcommands are still part of npm access and I don't see where they were ever deprecated.

~/D/n/c/b/main (latest|✔) $ npm -v
9.3.1
~/D/n/c/b/main (latest|✔) $ npm access -h
Set access level on published packages

Usage:
[...]
npm access grant <read-only|read-write> <scope:team> [<package>]
npm access revoke <scope:team> [<package>]

They are also included in the tests that ensure they result in actual http calls to the registry.

[jaswrks]

@wraithgar Thanks for confirming. So the docs state they are deprecated, though.
https://docs.npmjs.com/cli/v9/commands/npm-access

grant / revoke (deprecated): Add or remove the ability of users and teams to have read-only or read-write access to a package.

[wraithgar]

Looks like the docs weren't updated to reflect the new v9 api npm/cli#5445