toml
[dependencies]
serde = "1.0"Notes
The default registry used by Cargo is crates.io.
Rust CLI Dependencies, Features, and Workspaces
Dependency declarations, feature flags, workspace commands, and reusable patterns for larger Rust CLI projects.
Export
Copy the compact sheet, download it, or print it.
Download
`D` dense toggle · `C` copy all
Dependencies
Define registry, git, path, and dev dependencies.
toml
[dependencies]
mycrate = { git = "https://github.com/org/mycrate.git", branch = "main" }Notes
Git dependencies are useful for unreleased fixes or internal code.
toml
[dependencies]
common = { path = "../common" }Notes
Path dependencies are common in workspaces and local development.
Add dev-dependencies
Keep test-only crates out of the normal build graph.
tomlANYcargodependenciesdev
toml
[dev-dependencies]
assert_cmd = "2"
predicates = "3"Notes
Development dependencies are compiled for tests, examples, and benches.
toml
[build-dependencies]
cc = "1"Notes
Build dependencies are only available to the build script.
Features
Control optional code and dependency behavior.
toml
[features]
default = ["color"]
color = []
json = ["dep:serde_json"]Notes
Cargo features enable or disable optional functionality.
bash
cargo build --features json,colorNotes
Use a comma-separated feature list for the local package.
bash
cargo test --no-default-featuresNotes
Useful to verify optional code paths compile independently.
bash
cargo check --all-featuresNotes
Helpful in CI for validating the full feature matrix.
Workspaces
Group crates into one workspace and operate across members.
toml
[workspace]
members = ["crates/*", "xtask"]
resolver = "2"Notes
Workspaces let multiple packages share one lockfile and target directory.
bash
cargo build --workspaceNotes
A common command at the monorepo root.
bash
cargo test --workspaceNotes
Helps enforce repository-wide quality gates.
bash
cargo check -p xtaskNotes
Use `-p` or `--package` to focus on one workspace member.
bash
cargo test --workspace --exclude xtaskNotes
Useful when a member needs a different environment.
Common CLI crate recipes
Patterns often used in Rust command-line tools.
rust
use clap::Parser;
#[derive(Parser, Debug)]
struct Args {
#[arg(long)]
verbose: bool,
#[arg(long, default_value = ".")]
path: String,
}Notes
The `clap` ecosystem is a common choice for Rust CLI argument parsing.
rust
fn main() -> anyhow::Result<()> {
println!("hello");
Ok(())
}Notes
Returning `Result` from `main` is a clean pattern for CLI apps.
bash
RUST_LOG=info cargo runNotes
Many Rust apps use environment-controlled logging during development.
More in Rust CLI
Rust CLI Troubleshooting: CI, Environment, Build Scripts, and Publishing
Commands for debugging CI failures, environment mismatches, build script output, installation problems, and publish checks in Rust CLI projects.
Rust CLI Troubleshooting: rustup, Toolchains, Components, and Targets
Commands for fixing toolchain mismatches, missing components, and cross-compilation target issues in Rust CLI projects.
Rust CLI Troubleshooting: Tests, Doctests, and Documentation
Commands for debugging failing tests, capturing output, isolating flaky cases, and fixing documentation-generation issues in Rust CLI projects.
Rust CLI Troubleshooting: Dependencies, Features, and Lockfiles
Commands for analyzing dependency trees, feature activation, duplicate crates, and lockfile behavior in Rust CLI projects.
Rust CLI Troubleshooting: Manifest, Packages, and Workspaces
Commands and examples for debugging Cargo.toml issues, package selection mistakes, and workspace confusion in Rust CLI repos.
Rust CLI Troubleshooting: Build Errors and Diagnostics
Commands for investigating compiler errors, Cargo diagnostics, verbose output, and fix suggestions in Rust CLI projects.