{"action":"closed","issue":{"url":"https://api.github.com/repos/npm/npm/issues/11125","labels_url":"https://api.github.com/repos/npm/npm/issues/11125/labels{/name}","comments_url":"https://api.github.com/repos/npm/npm/issues/11125/comments","events_url":"https://api.github.com/repos/npm/npm/issues/11125/events","html_url":"https://github.com/npm/npm/issues/11125","id":126238178,"number":11125,"title":"npm shrinkwrap results in ECONNRESET errors with 3rd Party Registry (Follow-up)","user":{"login":"simonua","id":8005145,"avatar_url":"https://avatars.githubusercontent.com/u/8005145?v=3","gravatar_id":"","url":"https://api.github.com/users/simonua","html_url":"https://github.com/simonua","followers_url":"https://api.github.com/users/simonua/followers","following_url":"https://api.github.com/users/simonua/following{/other_user}","gists_url":"https://api.github.com/users/simonua/gists{/gist_id}","starred_url":"https://api.github.com/users/simonua/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/simonua/subscriptions","organizations_url":"https://api.github.com/users/simonua/orgs","repos_url":"https://api.github.com/users/simonua/repos","events_url":"https://api.github.com/users/simonua/events{/privacy}","received_events_url":"https://api.github.com/users/simonua/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2016-01-12T18:03:07Z","updated_at":"2016-01-13T21:37:58Z","closed_at":"2016-01-13T21:37:57Z","body":"This is a follow-up to issue [11117](https://github.com/npm/npm/issues/11117).\r\n\r\n@iarna, I was able to reproduce the ECONNRESET errors against our ProGet instance and captured everything with silly logging turned on. The attached log file has been scrubbed for our ProGet URL (the organization has been replaced with \"contoso\") and the username (\"foouser\"), but everything else should be original.\r\n\r\nI was not able to reproduce the 404s, but if I encounter that behavior again, I will either attach or create a new issue.\r\n\r\nWe make more than 1,000 resource requests for modules as part of the package we are installing. Not to put the cart before the horse, but if this indeed turns out to be a throttling issue, I don't suppose there's much we can do with ProGet at this time, and the two options we may have would be to a) wait until a throttling feature is added to the npm client, or b) use npm private modules or a different registry, correct?\r\n\r\nThanks very much again for checking into this!\r\n\r\n[npm-silly-scrubbed.txt](https://github.com/npm/npm/files/87730/npm-silly-scrubbed.txt)\r\n"}}