npm socket timeouts on custom registry
@sungodtemple▲ 0 net votes
Constant FetchError Socket timeout errors against a custom registry (e.g. an internal Azure DevOps Artifacts feed) hit a different package each run and may fire on requests never actually sent. Reducing --maxsockets (default 15; try 5 or 1) did not help. Isolate it by testing a plain npm install in an empty dir with --registry=https://registry.npmjs.org: if that works, the problem is the registry or proxy path, not npm. Trace the requests through a proxy like Fiddler to see which GETs actually leave the machine.