-
Notifications
You must be signed in to change notification settings - Fork 34
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
Add Deno and Node to extra implementers of various specs #35
Conversation
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.
Thanks for tackling this! Just a nit on the approach, but overall this seems fine and much appreciated.
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.
🎉 woo! thanks for doing this @lucacasonato
Talked to James, and have now added Node to the following specs:
Deno has been added to the following specs:
|
WebIDL would probably be a good one for Node.js also. We implement only in so far as it is relevant to the other specs but receiving notifications on changes there would be helpful. |
For Node you could also add import assertions, and possibly ES modules generally. |
ES modules are not specified here, but in TC39. Specific import assertions are not very relevant to Node I think, because Node likely won't implement most of the assertions specified other than JSON. (Same goes for Deno in this case). |
I was thinking of situations like this: whatwg/html#7342 |
@GeoffreyBooth Added "esm resolver" to node's and Deno's interest lists |
See whatwg/streams#1141 for more background on this.
I have not added Deno to
fetch
even though we implement it, because most changes in there are really not relevant to us in the slightest (CORS etc).