[Bug] Makes real network requests in Node 10
See original GitHub issueWorks fine in v6/v8: https://travis-ci.org/aaronjameslang/survey-monkey-streams/jobs/387636141
Very slow in v10: https://travis-ci.org/aaronjameslang/survey-monkey-streams/jobs/387636140
Running these tests offline locally gives {"errno":"ENOTFOUND","code":"ENOTFOUND","syscall":"getaddrinfo"}
Don’t have time to fix this rn, hopefully someone else can pick it up, or at least confirm. Thanks for the awesome module!
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:6
Top Results From Across the Web
5 ways to make HTTP requests in Node.js - LogRocket Blog
Make HTTP requests in Node.js using the native module as well as npm packages like Axios, Got, SuperAgent, and node-fetch.
Read more >TypeError: Network Request Failed #971 - mswjs/msw - GitHub
Describe the bug. I received this error whenever there's code error on the handler code. Environment. This unit testing running on Node ......
Read more >15 Common Error Codes in Node.js and How to Fix Them
1. ECONNRESET ... If this exception occurs when making a request to another server, you should catch it and decide how to handle...
Read more >Delays in HTTP requests via Node.js compared to browser
I see the delays under higher workloads, simple (low numbers of) requests work fine... So, probably there are some tweaks for the request...
Read more >Top 10 Most Common Node.js Developer Mistakes - Toptal
In this article, we will take a look at ten common mistakes that developers new to Node.js often make, and how they can...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
2.4.0 fixes this issue. Thanks for reporting.
Node 10 is now LTS. Does anyone have time to dig deeper and resolve this issue? See also #141, #157.