network: Don't transitively include tokio 0.2 in WASM
1) We don't specifically depend on Tokio codec impls 2) Conflating features in Cargo means that enabling Tokio runtime in the native environment will also do so in WASM, where it's obviously not implemented and causes a compilation error.
parent
efbc7877
Please register or sign in to comment