-
Notifications
You must be signed in to change notification settings - Fork 24
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
RE: Fixing DNS in Node.js #54
Comments
pimterry
pushed a commit
that referenced
this issue
Apr 23, 2024
* feat(HTD-36): add integration cta / hero * fix(HTD-36): change icons for new ones * fix(HTD-36): add missing keys * fix(HTD-36): make appear icons --------- Co-authored-by: Gerald Martinez <[email protected]>
pimterry
pushed a commit
that referenced
this issue
Apr 23, 2024
* feat(HTD-36): add integration cta / hero * fix(HTD-36): change icons for new ones * fix(HTD-36): add missing keys * fix(HTD-36): make appear icons --------- Co-authored-by: Gerald Martinez <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey! We saw your article here https://httptoolkit.com/blog/configuring-nodejs-dns/ and wanted to pass along our project Tangerine (which supports CacheableLookup).
It's faster than the native Node.js dns module according to our benchmarks (see README).
The text was updated successfully, but these errors were encountered: