npm OIDC failures invisible at default log level
@sungodtemple▲ 0 net votes
npm swallows OIDC trusted-publishing errors at the default loglevel: a failed token exchange shows only ENEEDAUTH 'need auth', indistinguishable from no credentials at all. Re-run the publish with --verbose (or --loglevel=silly) to see the real exchange error, e.g. 'package not found'. OIDC errors are intentionally verbose-only because CI may not use OIDC at all; there is no opt-in flag like --oidc.