cargo-edit
nexus-repository-cargo
Our great sponsors
cargo-edit | nexus-repository-cargo | |
---|---|---|
45 | 1 | |
2,985 | 63 | |
- | - | |
7.4 | 0.0 | |
2 months ago | 9 days ago | |
Rust | Java | |
MIT License | Eclipse Public License 1.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-edit
-
Hey Rustaceans! Got a question? Ask here (23/2023)!
“cargo add” from https://github.com/killercup/cargo-edit has that behavior, but not the built in one that was added to cargo
-
Is Rust's cargo-edit crate still relevant?
I have also noticed that the last commit of cargo-edit crate's GitHub repo (https://github.com/killercup/cargo-edit) was two days ago (pretty recent.) So it is probably relevant for a lot of people.
-
What are some useful tools for Rust?
cargo-upgrade from cargo-edit (somewhat more intentional than builtin update)
-
How to list upgradable crates programmatically
I've also tried cargo-upgrade from cargo-edit like so:
-
Hey Rustaceans! Got a question? Ask here (9/2023)!
You can also see how other crates do it. For example, cargo-edit is just like that - a single package with a library with a couple of small cli wrappers around it. You can compare their Cargo.toml to yours, maybe there is something different about them.
-
`toml` vs `toml_edit` (ie `toml` 0.6 is out)
Just to check, are you aware of cargo-edit's cargo-set-version or cargo-release?
-
Rust 1.66
Speaking of cargo remove, see also cargo-edit [0] from which adding and removing originally came, as well as cargo-binstall [1] which installs binaries rather than compiling from source every time. The binaries are updatable with cargo-update [2].
The latter two can replace a package manager for Rust related utilities, as I often find that those in OS package repositories are often not as up to date as directly from cargo.
[0] https://github.com/killercup/cargo-edit
[1] https://github.com/cargo-bins/cargo-binstall
[2] https://github.com/nabijaczleweli/cargo-update
-
TIL about cargo add
For context, it was/is part of cargo-edit crate which provides other nice functionalities as well. Hope all gets integrated in time.
-
how can I use same crate but with different features?
https://github.com/killercup/cargo-edit can use the F option
- `cargo-set-version` support for workspace inheritance released in cargo-edit 0.11.4!
nexus-repository-cargo
-
Adopting Rust in an Offline Environment?
I'm primarily a Go developer, and for that we use Sonatype Nexus to cache dependencies online, and we sync those offline to pull from. That works pretty well for us, and we use this for a bunch of languages like Ruby, C#, NodeJS, etc. But it looks like Nexus doesn't support Cargo, and the only community plugin I could find only supports hosting, while I need a proxy. I did see Artifcatory has some level of Cargo support, but we have to have an open-source solution. We also mirror the Ubuntu repositories, so we get our C/C++ libraries through that. I've noticed Rust dependencies in there, but they don't work through Cargo from what I've seen.
What are some alternatives?
cargo-outdated - A cargo subcommand for displaying when Rust dependencies are out of date
romt - Romt (Rust Offline Mirror Tool) aids in using the Rust programming language in an offline context.
Cargo - The Rust package manager
juniper - GraphQL server library for Rust
cargo-do - allows you to run multiple cargo commands in a row
cross - “Zero setup” cross compilation and “cross testing” of Rust crates [Moved to: https://github.com/cross-rs/cross]
cargo-dot - Generate graphs of a Cargo project's dependencies
n3dr - Nexus3 Disaster Recovery (N3DR) is a tool that is capable of downloading all artifacts from a Nexus3 server and to migrate them to another one.
cargo-script - Cargo script subcommand
cross - “Zero setup” cross compilation and “cross testing” of Rust crates
cargo-watch - Watches over your Cargo project's source.
cargo-make - Rust task runner and build tool.