cli
cli copied to clipboard
docs: document forceAuth option for libnpmpublish
Description
This PR documents the \orceAuth\ option for libnpmpublish, which is required when using automation tokens or when the \ oken\ option alone doesn't work.
Changes
- Added documentation for the \opts.forceAuth\ option in the options section
- Added a note and example showing how to use \orceAuth\ with automation tokens
- Clarified when to use \orceAuth\ instead of just \ oken\
Fixes
Closes #7091
Context
Users were experiencing 404 and 429 errors when trying to publish packages using automation tokens with libnpmpublish. The solution is to use \orceAuth: { token }\ instead of just \ oken, but this wasn't documented. This caused significant confusion as mentioned in issue #4250 and #7091.
The \orceAuth\ option is required in cases where the registry URL is not automatically detected from the token, which commonly happens with automation tokens.
Type of Change
- [x] Documentation update