Thanks for asking! Right now, we haven't prioritized WASM as a compilation target for Unison for a couple of reasons, but if you feel strongly that this would allow you to use Unison at your organization or job, be sure to drop a note in the comment thread for us to be aware of.

• WASM doesn't currently support Unison's model for effects, Abilities, which are based on continuations. There's an open discussion about adding continuation support to WASM here from the project maintainers. It's a great read if you're curious about effect handlers and what problems they solve for programming languages. As it stands, performing basic effectful operations in Unison would require some underlying support for continuations in WASM.
  • There's some interesting research in adding continuations: https://dl.acm.org/doi/10.1145/3426422.3426978, but we're hoping to see the research tested in practice before writing an interpreter.
• Garbage collection support in WASM is in active development. Here's the wasm gc MVP doc, if you're curious.

Once features like garbage collection and continuation support are more battle-tested, we could consider investing more time into a WASM backend. For now, the folks working on the compiler / interpreter have been focusing their time on performance improvements for the existing Unison runtime, and the JIT compiler.