[BUG] NPM does not show the URL in the console if a 401 occur.

[Kuinox]

What / Why

When running an npm ci, if a 401 occur while fetching the packages, the error is displayed in console, but the URL of the request (and the package requested) is present only in the log files.
When a 401 occur, i think the url and the package name are crucial information for the user.

When

Running npm ci, with bad(expired/wrong) credentials for a scope.

How

Current Behavior

Npm CI run and show a 401 error.

npm WARN prepare removing existing node_modules/ before installation
npm ERR! code E401
npm ERR! Unable to authenticate, need: [Private]

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\[Private]\AppData\Roaming\npm-cache\_logs\2019-11-07T10_06_48_484Z-debug.log

Steps to Reproduce

• Put bad credentials on a private scope.
• Run npm ci

Expected Behavior

npm should show the package that couldn't be downloaded, and the url that returned a 401.

[darcyclarke]

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.