Cargo
The Rust package manager (by rust-lang)
cargo-edit
A utility for managing cargo dependencies from the command line. (by killercup)
Our great sponsors
| Cargo | cargo-edit | |
|---|---|---|
| 129 | 23 | |
| 8,522 | 2,527 | |
| 3.3% | - | |
| 9.8 | 9.3 | |
| 3 days ago | 8 days ago | |
| Rust | Rust | |
| Apache License 2.0 | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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
Posts with mentions or reviews of Cargo.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-06-16.
-
Any active open source repos built using Rust that need development ?
Has anyone provided feedback on workspace inheritance yet?
-
Wasi dependencies in Cargo.lock
Cargo currently does not produce minimal lock files. During generation, it includes things like platform specific dependencies etc, which has been a blocker for other feature like platform specific cargo vendoring. The closest to a tracking issue is https://github.com/rust-lang/cargo/issues/5133 and a few other issues linked inside it.
-
Why are rustflags in target.cfg sections not applied?
Ah, there is an issue for this: https://github.com/rust-lang/cargo/issues/6858
- Ctrl+C, Ctrl+V
-
How to compile for native and wasm without erasing build artifacts?
I've encountered this before when trying to compile for different targets. I found https://github.com/rust-lang/cargo/issues/9239 which seems relevant. In my case a workaround was to pass --target explicitly when compiling for the host.
-
Is there any docs about crates.io API
Lurker here. Haven’t started to learn rust but wouldn’t this be self documenting by looking at cargo? I have a feeling there would be little other public endpoints outside of that. Very cursory look yields: https://github.com/rust-lang/cargo/blob/master/crates/crates-io/lib.rs
-
Rust's problematic reliance on GitHub
You may be interested in the work on an HTTP based index, https://github.com/rust-lang/cargo/issues/9069
-
Announcing Rust 1.61.0
Anybody knows when cargo-add will be distributed in stable cargo? Seems merged already.
I also just noticed a bug, which I reported here.
I created a feature request for the first thing.
cargo-edit
Posts with mentions or reviews of cargo-edit.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-05-08.
-
Problem understanding Crates
E.g. cargo-edit. It contains multiple binaries (and a library crate which you can't see below):
-
Rust from 0 to 80% for JavaScript Developers
> Use Cargo.toml instead of package.json. You’ll want to add them manually (instead of using a command like yarn add)
The cargo-edit tool gives you yarn-like commands to edit your packages. The main command, "cargo add", will be integrated into mainline cargo next update (I think).
-
cargo-edit v0.9 released!
"cargo add" should use dotted keys if already used in Cargo.toml #521
I hope you think of https://github.com/killercup/cargo-edit/issues/217
The PR enumerates some of the open questions. We felt there was enough uncertainty and little enough use that this is something that didn't need to be in the critical path for merging (ie not get in the way of everyone using all the other features)
-
Creating a CLI with Rust
Or, if you have cargo edit (which I prefer using), write right in your terminal:
-
How to follow the dependency of a dependency crate?
Workspaces + https://github.com/killercup/cargo-edit to automatically update the dependencies in the entire workspace.
-
Minor Semver Issue
I wanted to keep the focus on the idea and not have this be viewed as an attack on the person. However, the person has gone on to more publicly talk about their views (the linked users post) so its more clear who I was responding to so I'm willing to post the original discussion (look for the collapsed posts): https://github.com/killercup/cargo-edit/issues/126
-
What are your must install crates when starting a new project?
Lack of space was discussed and had challenges which led to the space.
What are some alternatives?
When comparing Cargo and cargo-edit you can also consider the following projects:
RustCMake - An example project showing usage of CMake with Rust
Clippy - A bunch of lints to catch common mistakes and improve your Rust code
crates.io - Source code for crates.io
cargo-outdated - A cargo subcommand for displaying when Rust dependencies are out of date
RustScan - 🤖 The Modern Port Scanner 🤖
opencv-rust - Rust bindings for OpenCV 3 & 4
cargo-check
rust-analyzer - A Rust compiler front-end for IDEs [Moved to: https://github.com/rust-lang/rust-analyzer]
cargo-script - Cargo script subcommand
overflower - A Rust compiler plugin and support library to annotate overflow behavior
windows-rs - Rust for Windows