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
Worker-rs installs a version of wasm-pack that can be incompatible with some systems due to curl or libc incompatibilities. There is an alternative solution in the end of this issue.
This is how the output looks like:
npm run dev --local
> dev
> wrangler dev --local
⛅️ wrangler 2.15.0
--------------------
Want to try out the next version of local mode using the open-source Workers runtime?
Switch out --local for --experimental-local and let us know what you think at https://discord.gg/cloudflaredev !
Running custom build: cargo install -q worker-build --version 0.0.9 && worker-build --release
Error: wasm-pack exited with status signal: 11 (SIGSEGV) (core dumped)
✘ [ERROR] Command failed with exit code 1: cargo install -q worker-build --version 0.0.9 && worker-build --release
If you think this is a bug then please create an issue at https://github.com/cloudflare/workers-sdk/issues/new/choose
There is a solution: you can overwrite the wasm-pack version that gets installed by worker-rs with curl/static-curl feature enabled. This builds curl into the binary, and fixes any possible incompatibilities.
Is there an existing issue for this?
What version of
workers-rs
are you using?0.0.15
worker-build
0.0.9 and 0.0.7Describe the bug
Worker-rs installs a version of wasm-pack that can be incompatible with some systems due to curl or libc incompatibilities. There is an alternative solution in the end of this issue.
This is how the output looks like:
There is a solution: you can overwrite the wasm-pack version that gets installed by worker-rs with
curl/static-curl
feature enabled. This builds curl into the binary, and fixes any possible incompatibilities.I will open a PR that would solve this issue by installing this feature by default. But I am not sure it should be merged.
Steps To Reproduce
In a more up-to-date Linux distro (like arch-based ones), run the getting started routine.
The text was updated successfully, but these errors were encountered: