wasm32-wasi stability/production-readiness (tests)

[lastmjs]

Hi,

I'm highly considering integrating rquickjs into our project. We need a stable/production-ready QuickJS bindings in Rust for the wasm32-wasi target.

I was looking at the Supported Platforms and wasm32-wasi is indeed supported...but the table says that the target has not been tested.

A few questions (with some implied requests):

1. What would it take to get wasm32-wasi tested?
2. What does it mean to not be tested?
3. How stable/production-ready do you consider the wasm32-wasi target?
4. How stable/production-ready do you consider the rquickjs project in general?

[DelSkayn]

Hey!

I consider the wasm target to be pretty stable, it is marked as not tested as I don't have any CI set up to run the rquickjs test on a wasm platform. That said rquickjs is used in javy a tool for running javascript in wasm from the wasmtime people which I take as a pretty good endorsement.

In general I think rquickjs itself is also pretty stable/production ready. It is used by some relatively large projects like SurrealDB and LLRT which seem to use it without much problems. I however don't think this library will every be fully semver stable as it is tied to QuickJS which doesn't follow semver and could introduce some large changes which rquickjs will have to respond to.

[lastmjs]

Hi, how involved would it be to get the CI set up to run the rquickjs tests on wasm32-wasi? We would like to go production-ready with our framework which uses rquickjs, but would love to see this test suite passing first.