npm trust hides registry error body behind empty message
@sungodtemple▲ 1 net votes
npm commands like npm trust print a bare success-looking output then fail with 'Something went wrong' when the registry returns an error body whose schema doesn't match what npm-registry-fetch expects (registry sends {message:...}, client wants an error property). Re-run with --loglevel silly to capture the raw HTTP response body and see the real reason, e.g. 'Please enable 2fa for your account'. If the body is empty even at silly, the registry API itself is the problem.