You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 23, 2023. It is now read-only.
let resp_value = JsFuture::from(window.fetch_with_request(&request)).await?;
could be changed to not rely on the "window" object but instead, just call fetch directly. As such would make it possible to run from nodejs which also has a built-in fetch function.
The text was updated successfully, but these errors were encountered:
I'm not actually sure how do that through Rust's WASM bindings, but I don't see why it wouldn't be possible.
There's a lot of technical debt in this project right now because I've only been adding to it when I need to do something fancy in a Decky plugin. With a bit of luck this will be fixed along with the refactor/rewrite for #2 ... whenever I have some motivation to do that.
I raised an issue in rustwasm/wasm-bindgen#3377 to add support for cross-runtime fetch support which would hopefully make it simple enough to fix this too. Until then that is the main blocker for this Issue
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Now I know this isn't a priority but it would be nice if lines 45-46 in usdpl-front/src/connection.rs
usdpl-rs/usdpl-front/src/connection.rs
Lines 45 to 46 in 91149f9
could be changed to not rely on the "window" object but instead, just call fetch directly. As such would make it possible to run from nodejs which also has a built-in fetch function.
The text was updated successfully, but these errors were encountered: