Repository navigation
Separate WebAssembly types from lib.dom.d.ts into their own file #826
Description
Currently, if you wish to use WebAssembly, you need to include lib.dom.d.ts, even in cases where that’s incorrect (e.g.: NodeJS or Deno).
The solution would be to move non‑web‑specific1 WebAssembly types to a new lib.wasm.d.ts file.
See also: #211
Footnotes
-
Web‑specific WebAssembly types are those defined in https://webassembly.github.io/spec/web-api/index.html.
Non‑web‑specific WebAssembly types are those defined in https://webassembly.github.io/spec/js-api/index.html. ↩
Reacted by Dolan Murvihill, Andrii Dieiev, Pierre-Marie Dartus, Eric K., Mathias Schreck, Andrew Haines, Thomas Wang, Noah Wilson, Sam Estep, Nam Se Hyun and 14 more
Reacted by Kagami Sascha Rosylight, Simon Schick, Dmitry Semigradsky, Benjamin Pasero and Michael
Activity
[-]Separete WebAssembly types from `lib.dom.d.ts` into their own file[/-][+]Separate WebAssembly types from `lib.dom.d.ts` into their own file[/+]Semigradsky commentedon Oct 26, 2020
+1
Currently I can't define
AbortController/AbortSignal/EventTarget/Eventfor node@15.x because typings includelib.dom.d.ts(with its own implementation ofAbortController/AbortSignal, etc.) (DefinitelyTyped/DefinitelyTyped#48981)ExE-Boss commentedon Oct 26, 2020
Dmitry Semigradsky (@Semigradsky) That’s unrelated to this.
Your case is happening because you’re defining them using
class EventTargetinstead ofinterface EventTarget { ... }anddeclare var EventTarget: EventTargetConstructor, but that depends on TypeScript language support: microsoft/TypeScript#39054 (comment) and microsoft/TypeScript#39504.