As mentioned in #26, bevy_midi should be able to compile to wasm using:
cargo build --target wasm32-unknown-unknown
However, this requires some work, as far as I understand, WebMIDI is a bit different from native implementation.
Some investigation is needed to find out how different it is. Does it require that bevy_midi have compile-time changes / create a feature for wasm? etc.
As mentioned in #26, bevy_midi should be able to compile to wasm using:
cargo build --target wasm32-unknown-unknownHowever, this requires some work, as far as I understand, WebMIDI is a bit different from native implementation. Some investigation is needed to find out how different it is. Does it require that bevy_midi have compile-time changes / create a feature for wasm? etc.
midirwhich bevy_midi uses for the backend has an example of how to run it in the browser: https://github.com/Boddlnagg/midir/tree/master/examples/browserWe should create an example as well in the same layout structure or using
cargo trunkfor when running the example