Christoph Herzog
Christoph Herzog
We don't have a fast path for vectorized IO in the `VirtualFile` implementation, which might be part of the slowness. But it's more likely that the `asyncify` wrapper and the...
@kobyhallx the error is pretty clear, Chrome forbids loading large wasm modules on the main browser thread. You need to offload the module parsing to a worker. Here is some...
I guess it would make sense to add an async version of `Module::new()` for the Javascript implemenetation, which uses `WebAssembly.compile()` under the hood. That would work similar to the `NativeEngineExt`,...
I believe taking inspiration from the new wasmer-js SDK should be sufficient.
Relevant backend query: ``` { getPackageVersionByHash () } ```
Hey @fschutt , long time now see, how are you doing? Thanks for the feedback. We just had a big revamp of the CLI... there is some fallout. The problem...
@XinyuZeng in particular, the wasmparer version needs to be updated across the whole repository so we don't have duplicate versions.
I've done something similar in the past by just copying the code in `juniper_warp` and adding my own logic in front. Making the integration code a bit more extendable would...
@relcodedev you need to specify `wasmer run --net` to enable networking. I don't see that in your posted CLI command.
Yeah that may well be a bug. Until we have time to investigate, you could run with `RUST_LOG=wasmer_wasix=trace wasmer run ...` to see a log of the syscalls, which would...