Include wasm based installation as a fallback option.

[DamianReeves]

I am using arm linux and arm windows versions of the moonbit tooling but installing it requires non-standard installation.
The blogpost here: https://www.moonbitlang.com/blog/moonbit-wasm-toolchain speaks to a method of installing the moonbit toolchain in these environments by using the following installation script (or following the instructions outlined):

curl -fsSL https://raw.githubusercontent.com/moonbitlang/moonbit-compiler/refs/heads/main/install.ts | node

It would be really awesome if moonup could incorporate this launch option.

[chawyehsu]

Supporting more architectures (ARM Linux / ARM Windows) in moonup itself isn’t difficult, it just requires adding new targets in the CI/CD pipeline. However, users can't get the list of MoonBit toolchains because it’s not provided upstream (moonbit-binaries).

After briefly reviewing the install script, I found that it builds the build tools (e.g. moon, moonrun, etc.) on-the-fly on the host during installation. In this situation, implementing a wasm toolchain fallback for moonup would therefore require some additional work.

If the upstream could provide prebuilt MoonBit buildtools separately, things would be much simpler. Otherwise, I might need to create a new repository to fetch the wasm compiler artifacts, build the corresponding buildtools via CI, and then pack and upload them to GitHub Releases for downstream to consume.

This would bascially be a replica of moonbit’s official distribution workflow but for targets not yet supported. It shouldn’t be technically challenging to implement, but it will depend on available time and manpower.