Open databasedav opened 4 months ago
Thank you for your experiments. I will attempt to enable WASM support likely after bevy 0.14 releases in the near future.
after some investigation, i've discovered that the CommandQueueSender
contained by the AsyncWorld
is closed within the body of the this future https://github.com/dlom/bevy-async-ecs/blob/a8a7d3c34bb6654cf710c5be2e5d1452777480ce/examples/basic.rs#L16-L25 on wasm, but not on linux
should be reproducible on this branch https://github.com/databasedav/bevy-async-ecs/tree/wasm_experimenting
run with these
rustup target install wasm32-unknown-unknown
cargo install wasm-server-runner
CARGO_TARGET_WASM32_UNKNOWN_UNKNOWN_RUNNER=wasm-server-runner cargo run --target wasm32-unknown-unknown --example basic
and navigate to the served url
note i also disabled a bunch of bevy features in the dev dependencies here https://github.com/databasedav/bevy-async-ecs/blob/2db817e65142800347897f9783ccef7bbfb75cf9/Cargo.toml#L23-L36, i think winit might have been causing a separate issue
Thanks for your effort, I will try to reproduce myself soon :+1:
just wanted to add some tracking for this
i believe this is blocked on this PR https://github.com/smol-rs/async-io/pull/153, however, when i update the
async-io
dependency toand try to run the basic example following these instructions https://bevy-cheatbook.github.io/platforms/wasm.html, i get the following on when navigating to the served url
on firefox
on chrome
i'm not sure if this is actually relevant to this crate, or i'm just doing something wrong, also wasn't able to find anything about the wgpu backend feature stuff