You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
When running npm install in normal mode without -d it sometimes reports fetch errors but finishes successfully. Install is successful because npm attempts fetching several times. However it's not clear from the logs.
I propose reporting fetch errors only when all the attempts fail. Another option is to log "fetch failed, will retry".
The text was updated successfully, but these errors were encountered:
Another option is to log "fetch failed, will retry".
This is what I think makes the most sense. If somebody wanted to put together a patch with this tweak to the error message (it probably belongs in npm-registry-client), it would be welcomed.
The default message is fine, but it doesn't get displayed by default anymore, because the default logging level is warn, and those messages were being logged at info, which is lower priority. Since these really are warnings, go ahead and log them as such. Landed as 9bb2c34.
When running
npm install
in normal mode without-d
it sometimes reports fetch errors but finishes successfully. Install is successful because npm attempts fetching several times. However it's not clear from the logs.I propose reporting fetch errors only when all the attempts fail. Another option is to log "fetch failed, will retry".
The text was updated successfully, but these errors were encountered: