ComponentizeJS
ComponentizeJS copied to clipboard
bytecodealliance
JS -> WebAssembly Component
Originally opened in the jco repository (https://github.com/bytecodealliance/jco/issues/668). Also posting here for visibility. Feel free to close one of them. --- Here is a minimal reproduction: ## Create the following files...
We have intermittent failures in the `fetch` builtin test caused by failing requests to `httpbin.org`. We should change to running our own local server instead, so we don't rely on...
Similar to `opts.wevalBin`, I propose adding `wizerBin`. Running downloaded binaries can cause issues with reproducibility, security, and compatibility - for example, the downloaded binary doesn't work on NixOS.
Having an empty resource: ```wit interface execution { resource join-set-id { // id: func() -> string; } new-join-set: func() -> join-set-id; } ``` Calling `new-join-set` from a JavaScript guest fails...
Hi! I've started to use ComponentizeJS for a small project and I'm rather excited at the possibility of allowing javascript as a way for wasm plugins in my program. I...
It would be great to support input sources as TypeScript directly that then get converted into JavaScript before running through componentization.
With the release of ComponentizeJS `v0.17.0` we seem to have a hard dependency on the target world wit importing `wasi:[email protected]`. This seems to be due to StarlingMonkey trying to call...
I'm doing some benchmarking, and while this might be apples to oranges, 1. Invoking quickjs as a wasmtime precompiled using `--eval console.log('hello world')` 1000 times takes approx 7-8s 2. Invoking...
Now that StarlingMonkey is seeking to use runtime environment variables and sockets we might add these to the enable/disable features. Alternatively, we might want a `debugger: true/false` ComponentizeJS option when...