Re: rust wasm in Debian
On October 22, 2025 3:00 am, Jeremy Bícha wrote:
> What is the purpose of the wasm targets for Debian?
with my downstream hat on:
we (Proxmox) use these extensively for (web) UI code compiled for the
browser (wasm32-unknown-unknown), but haven't upstreamed parts of the
stack that have no usage in Debian yet to keep the churn/load smaller
there..
with my Debian hat on:
the three main use cases I know of are
- web/browser (see above)
- as container bytecode target (no usage in Debian AFAIK)
- as plugin bytecode target (at least zellij, which weepingclown is
trying to package uses it like that, as well as zed-editor which has
an RFP as well)
> Can I disable targets like this?
>
> [target.'cfg(all(target_arch = "wasm32", not(any(target_os =
> "emscripten", target_os = "wasi"))))'.dependencies.js-sys]
I don't think that's a good strategy mid- to long-term, as I expect both
the plugin and web usage to become more interesting in Debian in the
near future.
> The rust-wasm-bindgen* packages are a pain to update since there are
> at least 5 that need to be updated together. Ubuntu infrastructure
> takes hours to publish binaries which means many Rust packages are
> unbuilable while those are built in sequence. Debian also suffers but
> not as dramatically. Ubuntu is currently working through the past 3
> months of Rust transitions simultaneously. 😭
ouch. so there is no incoming? but this also hurts any non-wasm related
transition, right? so shouldn't it rather be solved on the infra side
there?
> Several low-level Rust packages have a dependency on
> rust-wasm-bindgen. I'd like to meticulously remove these dependencies
> where possible.
see above..
Reply to: