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
feat: net.resolveHost #37853
feat: net.resolveHost #37853
Conversation
@indutny I went ahead and added backport requests for 24-x-y and 25-x-y, since that's also where the last .net PR was targeted. If that isn't right or you want to backport further, just let me know, I can add/remove as needed 😄 |
This sounds good to me. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
API LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
API LGTM
Release Notes Persisted
|
I was unable to backport this PR to "25-x-y" cleanly; |
I was unable to backport this PR to "24-x-y" cleanly; |
@codebytere has manually backported this PR to "25-x-y", please check out #38152 |
@codebytere has manually backported this PR to "24-x-y", please check out #38153 |
Description of Change
See #37690
This adds
net.resolveHost
method that usesdefaultSession
to resolve hosts (similar tonet.fetch
).cc @nornagon
Checklist
npm test
passesRelease Notes
Notes: Add net.resolveHost that resolves hosts using defaultSession object