`Failed to instantiate WASI: RuntimeError`
X7md opened this issue · comments
I try to run qjs
but I facing this error.
Uncaught Error: Failed to instantiate WASI: RuntimeError: `
at B2.wbg.__wbg_new_342a24ca698edd87 (Library.esm.min.js:25:11051)
at 0024ee5a:0x7c9d3
at 0024ee5a:0x19d5a
at s.instantiate (Library.esm.min.js:25:6746)
at main.mjs:20:12
reproduction:
https://github.com/X7md/wasmer-js-test
Related: #302
Wasmer-js currently fails to instantiate larger wasm modules on the main thread in Chrome.
Related: wasmerio/wasmer-js#302 Wasmer-js currently fails to instantiate larger wasm modules on the main thread in Chrome.
Yeah, I try on Worker, can't run qjs
unfortunately...
but my main.wasm
(Golang Hello World using TinyGo to wasi)... work fine, still don't know why.
Related: wasmerio/wasmer-js#302 Wasmer-js currently fails to instantiate larger wasm modules on the main thread in Chrome.
Yeah, I try on Worker, can't run
qjs
unfortunately...but my
main.wasm
(Golang Hello World using TinyGo to wasi)... work fine, still don't know why.
reproduction (With Worker):
Related: wasmerio/wasmer-js#302 Wasmer-js currently fails to instantiate larger wasm modules on the main thread in Chrome.
Yeah, I try on Worker, can't run
qjs
unfortunately...
but mymain.wasm
(Golang Hello World using TinyGo to wasi)... work fine, still don't know why.reproduction (With Worker):
Also can't bundle it in vite build (RollUp), but work on vite dev (esBuild)
This is weird.
We have published a new version 1.1.0... could someone verify that the issue is fixed or is still happening? Thanks!
for now, no more error.
but also no output for wasi.getStdoutString()
but I think this form my side so... I will close this as fixed.