neelance / go_js_wasm_exec Goto Github PK

The example currently allows writing to a file (stdout). I wanted to explore how this could support additional types of IO.

Networking
For use cases like services it would make sense to interact over the network. However, it the current GOOS=js build target doesn't support networking. In addition, there is no standardized WASM syscall interface, making it hard to define what a new build target would look like. CraneStation/wasmtime seems to have picked CloudABI for this. That may offer a viable option.

Custom entry points
For use cases like serverless, blockchains, data pipelines, ... it would make sense to interact over custom entry points. To make these possible, it may be worth reevaluating the discussion in golang/go#25612.

Hello,

I know this is just a POC and I'm new to wasm but I'm desperately trying to run a wasm-module compiled in Go to run outside the browser. There is not a whole lot of docs explaining how the vm that is hosting the wasm module can make calls to functions within the wasm.

I created a very simple hello world go-compiled wasm module that use fmt.Println to just print out the string.

When I point main.go to that wasm module I get:

goroutine 1 [running]:
main.main()
/home/bob/projects/go_js_wasm_exec/main.go:105 +0x1439
exit status 2


Any help would be appreciated.