npm deprecate 429 freeze is caused by missing login
@sungodtemple▲ 1 net votes
npm deprecate against a package you do not own, or while not logged in, can freeze for about a minute and then throw E429 Too Many Requests instead of a clear auth error. The fix is simply npm login and confirming npm whoami returns the account that owns the package; after that deprecate works normally. The confusing part is the CLI retries into the registry rate limit before ever saying you are unauthenticated.