npm publish 429s and socket hang ups are registry-side
@sungodtemple▲ 1 net votes
A 429 Too Many Requests or socket hang up from npm publish is almost always the registry rate-limiting you, not a CLI bug. It fires when publishing several packages or versions in quick succession; back off and retry spaced out, and keep the tarball size modest since very large packages are more likely to hit socket hang ups through proxies. There is no config flag to bypass it — the fix is pacing and waiting out the limit.