You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like the issue is something to do with the most recent Rust version update (1.82) which enables some flags from LLVM 19, and those instructions aren't supported from the (unmaintained) webassemblyjs.
From the Rust issue:
Yes Rust 1.82 would emit +reference-types in the target-features custom section of the output wasm (that section has always been there and it's just more features being added there). I believe that wasm-bindgen used that as an indication to automatically use other transforms that enables, for example, table.fill. That would be why wasm-bindgen first started "breaking" with Rust 1.82.
The current repository uses an older version of wasm-bindgen (0.2.93) to get around the bug, but the more permanent solution would be to wait until a new version of wasm-bindgen is released, which would include the relevant fixes.
The text was updated successfully, but these errors were encountered:
Relevant issues/PRs from external repositories:
It seems like the issue is something to do with the most recent Rust version update (1.82) which enables some flags from LLVM 19, and those instructions aren't supported from the (unmaintained)
webassemblyjs
.From the Rust issue:
The current repository uses an older version of
wasm-bindgen
(0.2.93) to get around the bug, but the more permanent solution would be to wait until a new version ofwasm-bindgen
is released, which would include the relevant fixes.The text was updated successfully, but these errors were encountered: