`npm outdated` suddenly throws a multitude of "Access token expired or revoked. Please try logging in again." notices

Problem

Starting yesterday evening, `npm outdated` started throwing lots of `Access token expired or revoked. Please try logging in again.` notices. This seems to happen for every local package in my npm workspaces TurboRepo. Apparently the `outdated` command tries to find newer versions for local packages as well: [code block] Googling this error message gave me literally zero results, so I dug deeper into the npm source code and found out that the message is returned from the registry.npmjs.org server itself as a response header and then logged as a notice: [code block] I suspect there has been a change yesterday on the npm registry servers which now adds this `npm-notice` header to every 404 returned by the npm registry. But it makes me wonder: Why does the outdated command check the registry for local packages in the first place? And does it really make sense to return this error when a package was just not found?