wasmer-js: wasm-terminal: `w.resolve is not a function` error introduced from v0.11.0
I’ve been messing around with running the python WAPM package using wasm-terminal in a similar way to how WebAssembly.sh works. I kept getting plagued with w.resolve is not a function from the process worker (once it’s been blobified) on running. Eventually I fixed this by downgrading to v0.10.0 after noticing that WebAssembly.sh uses v0.10.0 and everything just worked!
I’m having a lot of difficulty creating a clean reproduction of this bug. On my own project I have nailed it down to a difference between v0.10.2 and v0.11.0. I tried installing WebAssembly.sh locally but have not been able to get it to build. However I suspect that if you upgraded WebAssembly.sh to use v0.11.0 you would see the same issue when running the python WAPM package.
It’s also difficult to trace down where the error is actually happening, since I’m working with the minified version of the process worker.
Sorry for the vague bug report!
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 16 (12 by maintainers)
Thanks for chiming in @sfranzyshen!
@wasmer is not being abandoned, in fact is being revamped! Just with a bit more optimal implementation. We will preserve the same API that the current wasmer-js has. That means, for using WASI, for example will be done through the same API and package in NPM.
For the filesystem layer, it’s likely to no longer be based on memfs (like For @wasmer/wasmfs was), so the API on that case might differ a bit. Regarding wasm-terminal, it’s likely that the API will be improved, but still using xterm.js.
We are on the way to deprecating this repo in favor of a pure-Rust implementation targeting Node and the browsers via wasm-bindgen. All APIs should work the same with the same provided API. But that’s why you are not seeing that much progress on this repo.
We are already working on the new version, and updates should follow 😃
Closed the issue by mistake. The Rust implementation lives in the Wasmer repo and uses wasm-bindgen to run in the browser.
You can check the browser/node tests here: https://github.com/wasmerio/wasmer/blob/master/lib/wasi/tests/js.rs