fix: wrong dgram compatibility info
#150
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
kwhinnery
suggested changes
Oct 2, 2023
|
Thanks for this @hey-ab - made a few suggestions. I will go ahead and commit them unless you object, and merge this in the next ~day or so unless I hear from you. Thanks again! |
Co-authored-by: Kevin Whinnery <kevin.whinnery@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
That PR fix wrong compatibility info about
node:dgram. In fact, the realization is quite partial and most popular libraries usingdgramnot working in Deno.Proof: denoland/deno#18324 (comment)
Some issues with
dgram: https://github.com/denoland/deno/issues?q=dgram