Koute

This is, I think, an issue with the `wasm32-unknown-unknown` target itself, as `wasm32-unknown-unknown` currently doesn't support catching panics. You should use the `wasm32-unknown-emscripten` target for now if you want to...

Can you post an example which reproduces this?

Ah, right. `wasm-bindgen` won't work will `cargo-web` right now; I wouldn't be against making it work in the future though. (This would need some integration work as right now both...

@mvlabat I still haven't fully thought out how to integrate those two, but it is on my TODO list. There are a few ways we could go about here: *...

@alexcrichton Let's me quickly describe the current implementation of the underlying mechanism through which my `js!` macro works and maybe you can tell me if it would be acceptable to...

> And I think that'd all end up working? Doesn't the `#[wasm_bindgen]` macro use custom sections? If so then so constructed `js!` macro will be broken due to https://github.com/rust-lang/rust/issues/56639.

So is there actually a way to always force a custom section to be emitted or something? When I tried to use custom sections for my `js!` macro I tried...

This is something I do want to support, however I don't want to have to support a gazillion different runtimes. Currently `cargo-web` can actually emit two different runtimes using the...

The problem is that different people have different ideas on how this should look so it's hard to please everybody; also JS bundlers really don't like code like this (e.g....

That is something I've been thinking about, however I'm somewhat reluctant to depend on external non-Rust tools. (Supporting such tools across all three operating systems is a significant headache.) It...