-
Notifications
You must be signed in to change notification settings - Fork 68
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
Wasm support #73
Comments
Seems like Tokio can't be compiled for wasm32-unknown-unknown because of mio dependency, which is a big deal... I will probably create a small ipfs api for wasm for my own use, if I even can. |
@SionoiS Seems tokio is mainly used with hyper backend, so the reqwest backend should be a possible solution, no? |
Edit: Found this crate which compiles successfully to wasm. Some more testing needed though 🤔 |
https://lib.rs/crates/semtexzv-ipfsapi Not async which is weird when used on other targets. My code is at https://github.com/Defluencer/rust-defluencer/tree/develop/ipfs-api Not published though. |
I think it is async 🧐
...but thanks for this it's a good reference 😎 |
The best would be to implement a backend with reqwest. I may be more feasible than last year. I don't know if you got time to look into it. |
The one from @semtexzv is with reqwest |
I meant to say update rust-ipfs-api to include a backend that compile to wasm. |
Oh , now i get it! |
Opening this issue for tracking and to help me remember caveats.
seanmonstar/reqwest#1141
seanmonstar/reqwest#1151
seanmonstar/reqwest#1020
seanmonstar/reqwest#1013
Will have to wait for crate split #43, async multipart #58, and reqwest support #69.
The text was updated successfully, but these errors were encountered: