wasm releases

[kjvalencik]

Compiling as wasm would allow more direct integration with Actions instead of needing to publish compiled binaries and download with a bootstrap wrapper.

However, most useful actions need to interact with the network and filesystem. This would require a number of node.js bindgen wrappers.

[kjvalencik]

Basic idea:

• Create a node module that bootstraps the environment. Shims common APIs (e.g. node-fetch) and loads WASM (WASI?) from a known location (overridden with an input).
• Rust action npm install the bootstrap module and checks it in from node_modules. This is the action endpoint.
• Rust crate provides bindgen interfaces for the shims provided by the bootstrap code.
• Rust action compiles to wasm and commits the built code just like a JS action.

Other thoughts:

• The bootstrap code isn't rust specific. It works for any wasm action. Is there prior art?
• Can the bootstrap code be simplified? Can you wrap an action instead of needing to vendor the module?

[svenstaro]

Just stumbled across this. Are you aware of https://github.com/peter-evans/rust-wasm-action?