Tokio using Mio prevents compiling to WASM

[ERLindeman]

Compiling any code to wasm32-unknown-unknown fails to build because of the optional Mio dependency of Tokio. Would it be possible to disable that option and force Tokio to accomplish the same result without inheriting that child dependency?

[d-e-s-o]

I haven't looked into wasm support for a bit, but last I checked at least there was more to it than disabling an option. It was necessary to use proper replacement crates. Some of the offending crates may have added native support for wasm by now. Back in the day I had to replace hyper with something web-sys based, for example, but I recall at least one of the crates in the surrounding eco system to have had native wasm support in the works. That being said, we may be using too low level crates in some cases and would potentially have to switch them out for higher level counterparts that work on more platforms, if we were to support wasm use cases.