> If we’re not going to get direct access to the DOM, can we at least get the ability to just list the JS functions that our wasm will call? You mean like a li

> If we’re not going to get direct access to the DOM, can we at least get the ability to just list the JS functions that our wasm will call? You mean like a list of JS functions that are imported into the Wasm binary? This has been there since day one: (module ... (import "env" "foo" (func (;0;) (type 1))) (import "env" "bar" (func (;1;) (type 2))) ... ) > Everyone having to write all their own glue[*] is just nuts at this point. Did you mean for the specific programming language you use? If so then that seems like a problem for the language implementor, not a problem with Wasm. Rust has wasm bindgen, Emscripten has their thing, and so on.