You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Gotcha: There's also async iterables in the DOM. Those are defined later than ES2015.
Shouldn't we include those too?
So snap to ES2020 or something?
And what about Disposable/AsyncDisposable? Those might go into the DOM too.
DOM is effectively evergreen - we try to include things only when we have 2 distinct implementers shipping.
So maybe this should just pull in esnext?
On the other hand, you never know when implementers will have disagreements. So could just have explicit references to es2018.asynciterable and es2015.iterable. These additions are pretty rare.
dom.iterableanddom.asynciterableintsconfig.jsonMove Iterable/AsyncIterable into main DOM/WebWorker libs #62111
Consistent annoyance is that
lib: ["dom"]doesn't include"dom.iterable"or"dom.asynciterable".90402e7: If you have DOM and es2015, then we automatically add dom.iterable.
Move Iterable/AsyncIterable into main DOM/WebWorker libs #62111: Stick
dom.iterableinto the dom lib automatically, forcedomto includelib: es2015,dom.iterablereferencesdom(maybe doesn't have to, can just be empty).Disposable/AsyncDisposable? Those might go into the DOM too.DOM is effectively evergreen - we try to include things only when we have 2 distinct implementers shipping.
On the other hand, you never know when implementers will have disagreements. So could just have explicit references to
es2018.asynciterableandes2015.iterable. These additions are pretty rare.importwith{ type: "bytes" }Always creates an immutable default export that's a
Uint8Array.Think including images, wasm files, etc.
How do you model this? New syntax for ambient modules?
Mixed feelings on this.
We may not need new syntax, it is fine to just understand that
{ type: "bytes" }meansUint8Array.