-
Notifications
You must be signed in to change notification settings - Fork 426
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove transitive dependency on mio
#1283
Conversation
This allows projects targeting `wasm32-unknown-unknown` to compile. The `mio` dependency is being brought in via: `juniper_axum`→`axum`→`axum/tokio`→`tokio/net`→`mio`. By disabling the default features of `axum`, we disable its `tokio` feature.
Thanks! Can we get this added to CI so we don't accidentally regress? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A test in CI so we don't accidentally regress this would be great
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@SandroHc thanks!
Removes the transitive dependency on
mio
. This allows projects targetingwasm32-unknown-unknown
to compile. Fixes #1282.The
mio
dependency is being brought in via:juniper_axum
→axum
→axum/tokio
→tokio/net
→mio
. By disabling the default features ofaxum
, we disable itstokio
feature.axum
's comment onmio
:Reproduction Steps
rustup target add wasm32-unknown-unknown
cargo install cargo-generate && cargo generate --git https://github.com/rustwasm/wasm-pack-template
cargo add axum@0.7.5 --no-default-features
cargo add juniper@0.16.1
cargo build --target wasm32-unknown-unknown
cargo tree --target wasm32-unknown-unknown --invert mio
(no matches is what we want)cargo add juniper_axum@0.1.0
cargo build --target wasm32-unknown-unknown
cargo tree --target wasm32-unknown-unknown --invert mio
Build log & errors