team VS wasm-pack

Further down that GitHub issue, it mentions the problem has been fixed:

* https://github.com/rust-lang/rust/issues/71871#issuecomment-...

* https://github.com/rust-lang/rust/pull/79998

Weirdly though, there's another issue (opened prior) that's ongoing and seems to indicate things aren't fixed after all:

* https://github.com/rustwasm/team/issues/291

As for all the rust-wasm stuff, the dispute makes little sense. The "opposition" wants her to transfer publishing rights to a Github group actively being sunsetted and portraying it as a power struggle, yet this struggle is taking place in an issue Williams started in an effort to transfer ownership. Based on the last comments, it looks like publishing rights have been distributed to other members so the whole narrative is effectively moot.

I don't have direct WebAssembly experience (So far, my projects have either required stuff not compatible with WASI or been DOM-centric "must degrade gracefully with JavaScript disabled" stuff) but this thread looks like a good starting point for answering that question.

For a much simpler but less flexible approach there's wasm-pack for creating JS packages from Rust, and wasm-bindgen for easy interop. Both have very good documentation.

After four years, I found some time to pay that deb-tech (yes, quite a long time, eh). To make it fun I rewrote everything from scratch in SolidJS, which went smooth thanks to this amazing library p5js-wrapper. For WASM, C++ is still a good choice, but what about Rust? I did some research and found wasm-pack. A few lines in the cargo.toml file and we were ready to generate compiled + ready to import bytecode!

Support using wasm-pack in Worklets (particularly AudioWorklet) #689

If you're looking to use it to interface with node/browsers, then try wasm-pack.

Webassembly: wasm-bindgen 0.2.83 / wasm-pack 0.10.3

wasm-pack has bugs - it publishes a module which declares itself as a commonjs module. (You can fix that by manually adding "type": "module" in package.json). Then the web build should work with other bundlers. I opened an issue about this over a year ago. There's a PR and everything, but no movement :/

wasm-pack helps you build Rust-generated WebAssembly packages and use it in the browser or with Node.js.

Is the Rust WASM ecosystem being half dead better? wasm-pack and wasm-bindgen are barely maintained anymore, and trust me it's not because everything works flawlessly…

I've been learning Rust for the past few weeks and have been enjoying it a lot.

- The community is very helpful on Discord (https://discord.com/invite/rust-lang-community).

- The package ecosystem (crates.io) makes it very easy to find and import things, and they're consistently documented.

- There's a path to compiling on web via WebAssembly (https://rustwasm.github.io/wasm-pack/)

In a few weeks of learning the language, I managed to put together this visualization: https://twitter.com/admiralakk/status/1542560489091350529

But realistically, either Go or Rust will be fine. You should pick the one you're more likely to stick with and learn, even when it gets tough. I've found the community aspect to be very helpful, because then at least I know I'm not the only idiot out there.

There are various ways to set up a web project that uses Svelte, Wasm, and Rust. For example, wasm-pack from the rust-wasm group provides a template for simple HTML-CSS-JS applications. There are also several project templates for React or Svelte with Rust and Wasm.