Mget request: nonexistent package name results in non-specific 500 error.

[bafulton]

In a mget request, if npms does not recognize one of the package names, it fails with a 500 - internal server error. The error does not state which of the packages it did not recognize.

Context: I have a list of npm packages, some of which were created in the last few days. When POSTing to the mget endpoint with the list of packages, I receive a 500 error. I've established that it's related to the package '5g', which npms has no record of since it was just created 3 days ago (on July 7).

Npm package url: https://www.npmjs.com/package/5g
Npms search showing no '5g' package (as of July 10): https://npms.io/search?q=5g

Solutions: Ideally, npms would return the data for all recognized packages, with perhaps an 'errors' section that lists the unrecognized packages. More simply, it could just return a message with the 500 error stating which package was unrecognized, making it easier to resubmit the request with the offending package name removed.