fix: "unpublished by undefined" caused by tightened privacy policies.

[anurbol]

Now npm cli shows messages like this for unpublished projects when running npm view (note Unpublished by undefined):

> npm view my-package
npm ERR! code E404
npm ERR! 404 Unpublished by undefined on 2021-10-05T10:00:00.000Z
npm ERR! 404 
npm ERR! 404  'my-package' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)

This simple fix just removes the by undefined part.

[wraithgar]

The npm registry isn't the only registry the cli talks to, can this be something that shows the name if it exists? Also we'll need tests.

[wraithgar]

We'll likely need to change the "bug the author" copy cause that now makes no sense if there is no author listed.

[isaacs]

The "bug the author to publish it" copy is a relic from a time when lots of well-known JavaScript modules were "published" on github or someone's website, but not in the npm registry. So you'd have users that knew of a package, but that package wasn't in the registry, simply because no one had ever asked the author to publish it to npm.

These days, publishing to npm is a pretty normal thing for module authors to do, so if something isn't published, it's more likely you just spelled it wrong or you're looking in the wrong registry.

[wraithgar]

#4572