A forgotten one is webassembly.studio, an in-browser IDE for creating WASM projects with way less pain than other methods. It got discontinued the year I needed it for my school project. It was open source but I failed to rehost it myself and public mirrors only appeared after I spent days trying to make Emscripten work, tore my hair out over WebGL and then finally painfully built the whole thing with CSS (and a bit of JS; yes, it was indeed a disaster).
Nope. But I guess a mirror of WebAssembly Studio would still be the best starting point despite its slow development lately. The WAsm plugin for VSCodium was broken for me too.
Note that unlike JS, WASM won’t run from file:// URLs; you need to run a local http server or commit to an online repo to run your code. There might be an about:config option to change this but many IDEs (incl. WA Studio, presumably) come with servers for this reason.
A forgotten one is webassembly.studio, an in-browser IDE for creating WASM projects with way less pain than other methods. It got discontinued the year I needed it for my school project. It was open source but I failed to rehost it myself and public mirrors only appeared after I spent days trying to make Emscripten work, tore my hair out over WebGL and then finally painfully built the whole thing with CSS (and a bit of JS; yes, it was indeed a disaster).
Do you still use WASM? I’ve been exploring the space and wasn’t sure what the best tools are for developing in that space.
Nope. But I guess a mirror of WebAssembly Studio would still be the best starting point despite its slow development lately. The WAsm plugin for VSCodium was broken for me too.
Note that unlike JS, WASM won’t run from
file://URLs; you need to run a local http server or commit to an online repo to run your code. There might be anabout:configoption to change this but many IDEs (incl. WA Studio, presumably) come with servers for this reason.