We had issues in the browser calling into a WASM component, and eventually tracked it down to cargo-component v0.21.0 on (as far as we can tell) Apple Silicon. The built WASM seems to have issues in the adapter/shims, leading to call issues.
Issue logged here: https://github.com/bytecodealliance/cargo-component/issues/398
We've narrowed this down a lot, but if you need any more info or anything in the issue is unclear, we're happy to help further.
This was originally submitted to jco (and discussed here in zulip), so some context (you can see some error messages in there, though you'll have to ignore the JS-related bits of the stack trace):
https://github.com/bytecodealliance/jco/issues/634
#jco > Sudden transpiled wasm component error in browser
And for those who are going to look into the diff:
https://github.com/bytecodealliance/cargo-component/compare/v0.20.0...v0.21.0
Tracing this further, adapters are updated from v24 -> 29.0.1 here https://github.com/bytecodealliance/cargo-component/commit/241996c1d22c3c563048ec1b382cf72b1650860b
Last updated: Dec 06 2025 at 06:05 UTC