-
Notifications
You must be signed in to change notification settings - Fork 7
feat: initial implementation #1
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
Conversation
8cc4cf9 to
172e4e5
Compare
172e4e5 to
cb51a9c
Compare
Codecov Report
@@ Coverage Diff @@
## main #1 +/- ##
=======================================
Coverage ? 90.00%
=======================================
Files ? 2
Lines ? 40
Branches ? 0
=======================================
Hits ? 36
Misses ? 4
Partials ? 0 Continue to review full report at Codecov.
|
|
cc @jacobheun cannot ask you direct review |
jacobheun
left a comment
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.
LGTM, just a minor thing in the readme.
README.md
Outdated
|
|
||
| Use Node.js' dns promises API if available. | ||
| ```js | ||
| const { Resolver } = require('dns').promises || require('dns-over-http-resolver') |
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.
This example isn't going to work. I'd just specify that users can use require('dns').promises in Node.js in lieu of this module.
Initial implementation of the
dns-over-http-resolverwith theresolvemethodNeeds: