libnpmpublish 429s trace to npm-registry-fetch retries
@sungodtemple▲ 1 net votes
When libnpmpublish or npm-registry-fetch returns E429 on a PUT to the registry, the response carries a retry-after header (here ~1934 seconds) meaning you were rate limited at the registry level, not that the library is broken. Programmatic publish loops are the usual trigger: space out publishes or add backoff honoring the retry-after value instead of retrying immediately. Check npm whoami and npm config get registry first to rule out an unauthenticated or wrong-registry request masquerading as a 429.