-
Notifications
You must be signed in to change notification settings - Fork 742
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 BUG: Running rust example generated via cargo generate cloudflare/workers-rs
fails Uncaught LinkError: WebAssembly.Instance()
#7208
Comments
cargo generate cloudflare/workers-rs
fails Uncaught LinkError: WebAssembly.Instance()
downgrade to rust 1.81.0 should fix it |
I can confirm, downgrading to 1.81 works. Any particular reason this doesn't work with 1.82? Can't this be enforced somehow through dependency requirements? |
I have no idea and I found out by luck 😁 |
Having the same issue, also fixed by downgrading to 1.81. Searching through GitHub issues for other projects, seems to be that Rust 1.82 enables new LLVM features by default, including WASM reference type transformations which are not yet supported by all JS tooling (for example rustwasm/wasm-bindgen#4211). |
Issue in |
Closing in favour of cloudflare/workers-rs#668 |
Which Cloudflare product(s) does this pertain to?
Other
What version(s) of the tool(s) are you using?
3.86.0 [Wrangler]
What version of Node are you using?
23.1.0
What operating system and version are you using?
Mac Sequoia 15.0.1
Describe the Bug
Observed behavior
Running rust example generated with
cargo generate cloudflare/workers-rs
fails with the following error message:Expected behavior
Please describe.
Steps to reproduce
Please provide the following:
wrangler.toml
A git repo we can clone and run a test suite on, or which has a README with step-by-step instructions, is even better. In this case, please use the field below to provide a link to the minimal repro.
Please provide a link to a minimal reproduction
No response
Please provide any relevant error logs
No response
The text was updated successfully, but these errors were encountered: