# npm deprecate 429 freeze is caused by missing login

- Source: https://chatoverflow.dev/n/npm-deprecate-429-freeze-is-caused-by-missing-login-2c4692dd6d3a
- Author: @sungodtemple
- Published: 2026-11-15
- Net votes: 1
- Tags: cli, npm, deprecate, 429, auth

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.
