Scroll to navigation

CARGO-ADD(1) General Commands Manual CARGO-ADD(1)


cargo-add - Add dependencies to a Cargo.toml manifest file


cargo add [options] crate...
cargo add [options] --path path
cargo add [options] --git url [crate...]


This command can add or modify dependencies.

The source for the dependency can be specified with:

crate@version: Fetch from a registry with a version constraint of "version"

--path path: Fetch from the specified path

--git url: Pull from a git repo at url

If no source is specified, then a best effort will be made to select one, including:

•Existing dependencies in other tables (like dev-dependencies)

•Workspace members

•Latest release in the registry

When you add a package that is already present, the existing entry will be updated with the flags specified.

Upon successful invocation, the enabled (+) and disabled (-) features <> of the specified dependency will be listed in the command's output.


Source options

--git url

--branch branch

Branch to use when adding from git.

--tag tag

Tag to use when adding from git.

--rev sha

Specific commit to use when adding from git.

--path path

--registry registry

Name of the registry to use. Registry names are defined in Cargo config files <>. If not specified, the default registry is used, which is defined by the registry.default config key which defaults to crates-io.

Section options



--target target


Dependency options

--rename name





--features features

Space or comma separated list of features to activate <>. When adding multiple crates, the features for a specific crate may be enabled with package-name/feature-name syntax. This flag may be specified multiple times, which enables all specified features.

Display Options

-v, --verbose

Use verbose output. May be specified twice for "very verbose" output which includes extra output such as dependency warnings and build script output. May also be specified with the term.verbose config value <>.

-q, --quiet

Do not print cargo log messages. May also be specified with the term.quiet config value <>.

--color when

Control when colored output is used. Valid values:

auto (default): Automatically detect if color support is available on the terminal.

always: Always display colors.

never: Never display colors.

May also be specified with the term.color config value <>.

Manifest Options

--manifest-path path

Path to the Cargo.toml file. By default, Cargo searches for the Cargo.toml file in the current directory or any parent directory.

Common Options


If Cargo has been installed with rustup, and the first argument to cargo begins with +, it will be interpreted as a rustup toolchain name (such as +stable or +nightly). See the rustup documentation <> for more information about how toolchain overrides work.

--config KEY=VALUE or PATH

Overrides a Cargo configuration value. The argument should be in TOML syntax of KEY=VALUE, or provided as a path to an extra configuration file. This flag may be specified multiple times. See the command-line overrides section <> for more information.

-h, --help

Prints help information.

-Z flag

Unstable (nightly-only) flags to Cargo. Run cargo -Z help for details.


See the reference <> for details on environment variables that Cargo reads.


0: Cargo succeeded.

101: Cargo failed to complete.


1.Add regex as a dependency

cargo add regex

2.Add trybuild as a dev-dependency

cargo add --dev trybuild

3.Add an older version of nom as a dependency

cargo add nom@5

4.Add support for serializing data structures to json with derives

cargo add serde serde_json -F serde/derive