cargo-outdated
cargo-hack
cargo-outdated | cargo-hack | |
---|---|---|
7 | 4 | |
1,141 | 540 | |
- | - | |
6.7 | 9.3 | |
about 1 month ago | 9 days ago | |
Rust | Rust | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cargo-outdated
-
What are some useful tools for Rust?
cargo-outdated
-
How to list upgradable crates programmatically
I've tried to use cargo-outdated like so:
-
My Rust development workflow (after 3+ years)
Thanks to cargo and the community, project maintenance is straightforward in rust. You'll need to install cargo-outdated and cargo-audit:
-
Mental models for learning Rust
Use the automated tools to assist you in the maintenance of your projects: rustfmt, clippy, cargo update, cargo outdated and cargo-audit.
-
5 useful Cargo Plugins
I'd add cargo-outdated for checking for outdated dependencies. cargo-tree is also useful, but that's built into cargo itself for some time already.
-
Announcing `cargo supply-chain`: Know whom you trust
Some combination of cargo-outdated and cargo-msrv could probably do this in a slightly more manual fashion.
-
[Utility] Announcing version-checker - It Does What It Says on the Tin and More, Trust Me
So it merges functionality of cargo-outdated and cargo-audit?
cargo-hack
-
What are some useful tools for Rust?
cargo-hack for workspaces or projects that make heavy use of crate features
-
Is there a known way to minimize features of dependencies after the code is done?
When I'm managing cargo flags myself I have also found cargo-hack useful to make sure that all of my possible combos still build and pass tests. Sometimes that's helped me find an implicit feature I needed to declare.
-
How to write generic code for both thread-local and concurrent modes?
As a note for OP, be sure to not try to use this approach for code that's intended to be mutually-exclusive approaches. Code based on features should be designed so that any combination of crate features can be enabled simultaneously, including zero or all of them. Ideally the crate should always build and run under any permutation - if you want a way to test this exhaustively you can run your tests via cargo-hack.
-
PSA - Most Rust tooling runs only on the default feature set and current platform if no special steps are taken
For features: You can use cargo-hack or cargo-all-features to run on all feature combinations.
What are some alternatives?
cargo-check
cargo-all-features - A Cargo subcommand to build and test all feature flag combinations.
Cargo - The Rust package manager
cargo-sweep - A cargo subcommand for cleaning up unused build files generated by Cargo
cargo-edit - A utility for managing cargo dependencies from the command line.
cargo-cache - manage cargo cache (${CARGO_HOME}, ~/.cargo/), print sizes of dirs and remove dirs selectively
cargo-script - Cargo script subcommand
cargo-whatfeatures - a simple cargo plugin to get a list of features for a specific crate
cargo-watch - Watches over your Cargo project's source.
just - 🤖 Just a command runner
overflower - A Rust compiler plugin and support library to annotate overflow behavior
rat-rs - A simple cli tool to fetch transports schedules on the Ile-de-France région