-
Notifications
You must be signed in to change notification settings - Fork 257
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unknown import: __wbindgen_placeholder__::__wbindgen_cb_drop
has not been defined
#544
Comments
Edit: I got it to compile by removing reqwest, but this neuters the functionality. New request for help: How do I get the reqwest functionality without breaking wasi? |
I have a similar issue, although my error is:
Haven't traced it down to a particular dependency yet, but thats my next step. Would be ideal if this could be a compile time error (with some identifying information about what exactly introduces the issue) instead of a runtime error. |
Those symbols are coming from bindings created by the They are not implemented by wasmtime, and they won't be. |
I think the confusion, at least on my end, comes from the fact that this |
Sorry that tripped you up. That README was written in 2019 when wasm-bindgen and the ideas of interface types were radically different. Its use of wasm-bindgen is super out of date at this point, the upstream wasm-bindgen has moved on and (as far as I can tell) eliminated that obsolete interface types implementation. wasm-bindgen is a rustwasm group project, which isn't part of the Bytecode Alliance. So, we should probably remove that functionality from cargo-wasi and its docs, when someone gets a chance. cc @alexcrichton In the meantime, the name "interface types" has been subsumed by "component model". The term "interface types" only lives on in the .wit file extension, which is mostly because that extension had been reserved back in the interface types days and it seemed appropriate enough for use. |
Thanks for the heads up, I've opened an issue about archiving |
Hello,
I am trying to build a package
halo2_backend
I am working on and import it into javascript.I can build the package with
cargo build --lib --release --package noir_halo2_backend_pse --target wasm32-wasi
. However, when I try to initialize usingwasmer-js
orwasi-js
, or if I try to use wasmtime by the cli, it always produces the same error:I've tried removing as many references to wasm-bindgen in a separate branch, including sub-dependencies, but have not progressed. Any suggestions on how I debug this issue would be greatly appreciated!
The text was updated successfully, but these errors were encountered: