Publish fails with wierd error when the NPM key fails

[josephjclark]

I spent half a morning chasing this strange publish error:

npm notice Publishing to https://registry.npmjs.org/ with tag latest and public access
npm ERR! code E404
npm ERR! 404 Not Found - PUT https://registry.npmjs.org/@openfn%2fdeploy - Not found
npm ERR! 404 
npm ERR! 404  '@openfn/[email protected]' is not in this registry.
npm ERR! 404 
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

When trying to publish @openfn/deploy, I get an error saying @openfn/deploy is not found. Of course it's not found, I'm trying to deploy it you berk!!

Turns out that this is a problem with npm auth. It throws the wrong message: what this really tells you is that the API key we use to publish ti NPM has expired.

I'd like to add better messaging for this somewhere but I don't really know how. This issue will hopefully serve as a reminder.