Luca Casonato

It is working for me: https://gist.github.com/lucacasonato/60311fb6e00ccd9e6be63ff95adb6fb0

Oh I see this is about code blocks in JSDoc blocks in TS files

Fixed by #23915

@MattiasBuelens Updated! I am planning to submit a PR to `webidl2js`, similar to what I've done for `widlparser` already. EDIT: PR for webidl2.js: https://github.com/w3c/webidl2.js/pull/775

Moving over the question of whether this API should support `async iterable or DOMString`, or just `async iterable` as an argument (from https://github.com/whatwg/webidl/pull/1397#issuecomment-2020386670). In the current streams spec, strings are...

I have addressed @nicolo-ribaudo's review comment by removing the race condition between notification and read of the value in the module map. PTAL again @annevk. Note that the behaviour here...

@domenic I have updated the change to also not cache of mime type errors. --- @nyaxt Thanks for the feedback. The change to callback was necessary to be able to...

Add this to the top of `01_core.js` and compile: ```js if (typeof SharedArrayBuffer === "undefined") { throw new TypeError("SharedArrayBuffer is not available"); } ```

> FinalizationRegistry is not supposed to be used during snapshotting so perhaps that's why it's not visible. I understand that it shouldn't be used, but I still need access to...

Not breaking, so we're not going to do this for 2.0. Good suggestion though - we're considering this for a broader `--allow-net` revamp.