I use cargo-outdated on all of my Rust projects, and find it very useful. On a private project I've been playing with using bevy, and I've found that for some reason cargo-outdated takes so long to run that I can't use it on a regular basis as a part of my workflow automation.
I thought I'd start by filing the issue in case something jumps out that could be solved.
I've created a bare-bones repo with some common libraries that are paired with bevy. When I comment out different libraries, it gets faster, but still seems very slow compared with my usage on other projects.
I use
cargo-outdatedon all of my Rust projects, and find it very useful. On a private project I've been playing with using bevy, and I've found that for some reasoncargo-outdatedtakes so long to run that I can't use it on a regular basis as a part of my workflow automation.I thought I'd start by filing the issue in case something jumps out that could be solved.
I've created a bare-bones repo with some common libraries that are paired with bevy. When I comment out different libraries, it gets faster, but still seems very slow compared with my usage on other projects.
https://github.com/sax/outdated-bevy
Only bevy: ~1.5s
I would love to help debug or contribute a fix, but I'm not sure where to start with profiling this to figure out what's going on.