search

whatwg / spec-factory

WHATWG Standard repository templates and infrastructure
Creative Commons Zero v1.0 Universal
34 stars 33 forks source link

Add Deno and Node to extra implementers of various specs #35

Closed lucacasonato closed 2 years ago

lucacasonato commented 2 years ago

See https://github.com/whatwg/streams/issues/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).

lucacasonato commented 2 years ago

Talked to James, and have now added Node to the following specs:

Deno has been added to the following specs:

jasnell commented 2 years ago

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.

GeoffreyBooth commented 2 years ago

For Node you could also add import assertions, and possibly ES modules generally.

lucacasonato commented 2 years ago

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).

GeoffreyBooth commented 2 years ago

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: https://github.com/whatwg/html/issues/7342

lucacasonato commented 2 years ago

@GeoffreyBooth Added "esm resolver" to node's and Deno's interest lists

annevk commented 2 years ago