You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
More suggestions welcome, a good place to start is a timings report by cargo of the entire workspace (minus dev-dependencies): cargo build --workspace --all-features --timings. Once you have identified a (ideally heavy) dependency that we might not need, investigate with cargo tree -i -p <dependency> where it comes from.
The text was updated successfully, but these errors were encountered:
Might it be possible to get rid of the async-std (optional) dependency? I'd guess the ecosystem has moved on to tokio these days, with the last commit in async-std being 9 months ago: async-rs/async-std@bf316b0.
I think this could help cutting down some more dependencies as well.
I am not following the async-std development but I'd consider that one too established to remove.
Plus, it is optional as you said. I think it would be more fruitful to investigate for dependencies in our protocol crates like yamux, gossipsub or kademlia.
Might it be possible to get rid of the async-std (optional) dependency? I'd guess the ecosystem has moved on to tokio these days, with the last commit in async-std being 9 months ago: async-rs/async-std@bf316b0.
I think this could help cutting down some more dependencies as well.
We can cut down some dependencies by moving all our tests and examples to tokio. async-std is heavily feature-flagged, meaning we can reduce our dependencies by only activating the bare minimum features needed in the various transports and libp2p-swarm.
thomaseizinger
changed the title
Tracking issue: Reduce dependency tree
Reduce dependency tree
Sep 19, 2023
I'll record various efforts in here to reduce the size of our dependency tree where possible.
Tasks
strum
dependency #3513derive_builder
dependency webrtc-rs/webrtc#411webrtc-rs
tostr0m
#3659More suggestions welcome, a good place to start is a timings report by cargo of the entire workspace (minus dev-dependencies):
cargo build --workspace --all-features --timings
. Once you have identified a (ideally heavy) dependency that we might not need, investigate withcargo tree -i -p <dependency>
where it comes from.The text was updated successfully, but these errors were encountered: