-
Notifications
You must be signed in to change notification settings - Fork 30.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Global fetch produces unhelpful Error for ENOTFOUND #42804
Labels
fetch
Issues and PRs related to the Fetch API
Comments
This seems to be a bug of |
reopen as we need to update |
Seeing this error also. update to what version? does anyone know the cause? @meixg |
This was fixed in #42939 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
v18.0.0
Platform
Linux kevinolos 5.18.0-rc3 #197 SMP PREEMPT_DYNAMIC Mon Apr 18 07:08:40 MDT 2022 x86_64 GNU/Linux
Subsystem
http
What steps will reproduce the bug?
Run
node -e "fetch('http://invalid')"
How often does it reproduce? Is there a required condition?
100% reliable.
What is the expected behavior?
A helpful error, such as the one produced by
undici
:What do you see instead?
An error indicating that fetch failed with a cause of
Error: [object Object]
:Additional information
No response
The text was updated successfully, but these errors were encountered: