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, 2021. It is now read-only.
functionlatest(name,spec,done){varpath=encodeURI('/'+name+'/'+spec)http.get({hostname: 'registry.npmjs.org',path: path},function(res){varbuf=''res.on('data',function(data){buf+=data})res.on('end',function(){if(buf)done(null,JSON.parse(buf))elsedone(newError('received an empty response for '+path))})res.on('error',done)})}
Most of the time its fine but it gets called hundreds of times and usually one request will have this problem. If I rerun the program immediately it typically will have the same problem on a request for the same module it had problems with last time. If I wait a minute or so It will come right but then usually another module becomes the problem. I have been able to reproduce with curl but often it works with curl and not node. Yet npm view always works. This used to be pretty reliable. Has the HTTP API changed?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The function that makes the requests is this one:
Most of the time its fine but it gets called hundreds of times and usually one request will have this problem. If I rerun the program immediately it typically will have the same problem on a request for the same module it had problems with last time. If I wait a minute or so It will come right but then usually another module becomes the problem. I have been able to reproduce with curl but often it works with curl and not node. Yet
npm view
always works. This used to be pretty reliable. Has the HTTP API changed?The text was updated successfully, but these errors were encountered: