[FEAT] Support WASM

[Kaamkiya]

Is your feature request related to a problem? Please describe.

No, it would just be awesome to play these in the browser.

Describe the solution you'd like

Make these games compatible with WebAssembly, so that instead of requiring a terminal, they can be played in a browser as well.

Describe alternatives you've considered

There really aren't any.

Additional context

https://go.dev/wiki/WebAssembly

[gikaragia]

Hey @Kaamkiya haven't looked at WebAssembly before, I'd be interested to pick this one up. Can you assign?

[Kaamkiya]

@gikaragia Have fun! If you need help or anything with this, LMK.

[gikaragia]

Here is what I found after taking a quick look.

There are currently two options to compile the code to WASM, the official one and TinyGo.

For the first option, we need to jump through a few hoops to compile the bubbletea libraries (basically providing stubs for JS env as outlined here), but the compiled file is eventually produced. Its size is 6.1MB, which is not ideal. But the worst thing is that it still doesn't work, probably because there is no thread support yet in WebAssembly.

As for TinyGo, I encounter the following error when I compile:

wasm-ld: error: lto.tmp: undefined symbol: os/signal.signal_recv
wasm-ld: error: lto.tmp: undefined symbol: os/signal.signal_enable
wasm-ld: error: lto.tmp: undefined symbol: os/signal.signal_disable
wasm-ld: error: lto.tmp: undefined symbol: os/signal.signalWaitUntilIdle

This error might be fixed in the next release, but still, I don't think that it's possible to run bubbletea with it, as again, there is no support for threading.

We should probably reconsider this when there is better support for Go in WebAssembly.

[Kaamkiya]

Yeah, that makes sense. It seemed really hard to implement when I first looked which is why this was on backlog for so long.

[gikaragia]

Something that might be possible to is to export somehow the game code (without every or some of the bubbletea dependencies) and reimplement basically the bubbletea code in JS.

Then we could call the compiled Go libraries in the browser, but yes, it probably needs a lot of work as you said.