daxpedda

> That also means we don’t immediately need to have this merged if you prefer; we can wait until we’re a bit further along. Especially for adding a new target,...

> To clarify, are you looking for another current maintainer to lead the discussion here? Or are you looking for me to commit to maintaining this feature long-term after it's...

@CryZe > This by itself isn't really a problem, but `webpack`, or rather its `webassemblyjs` dependency is mostly unmaintained and does not currently support the `reference-types` proposal. > > @daxpedda...

While I wouldn't mind holding off until then, I would like to know how this is going to play out in the future. What do we do when LLVM enables...

I went ahead and implemented the proposal from https://github.com/rustwasm/wasm-bindgen/issues/4211#issuecomment-2444501491 in #4235: reference type proposal transformations aren't enabled by default for the bundler target. Please let me know if this addresses...

That is a different error entirely. My first guess is a different CLI and `wasm-bindgen` version, but that should be caught by the hash check. Could you try using Rust...

`webpack` (more precisely `webassemblyjs`) seems to now support reference-types, but I'm unsure why `wasm-pack` is still failing. So these are all the use-cases that have surfaced so far: - `wasm-pack`...

The next release is going to not apply reference type transformation when using the bundler output, which should fix this. However, I'm not sure what that `strip` usage is about,...

With #4253 I consider this issue resolved. To summarize: this is not a `wasm-bindgen` problem but a Rustc one, which enables reference-types by default. While it is true that the...

Yep! Thanks!