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

       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”

       •  --pathpath: Fetch from the specified path

       •  --giturl: 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
       <https://doc.rust-lang.org/cargo/reference/features.html> of the specified dependency will be listed in
       the command’s output.

       See thereference <https://doc.rust-lang.org/cargo/reference/environment-variables.html> for details on
       environment variables that Cargo reads.

        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

        5. Add windows as a platform specific dependency on cfg(windows)

               cargo add windows --target 'cfg(windows)'

       •  0: Cargo succeeded.

       •  101: Cargo failed to complete.

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

Sourceoptions--giturlGitURLtoaddthespecifiedcratefrom
           <https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#specifying-dependencies-from-git-repositories>.

       --branchbranch
           Branch to use when adding from git.

       --tagtag
           Tag to use when adding from git.

       --revsha
           Specific commit to use when adding from git.

       --pathpathFilesystempath
           <https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#specifying-path-dependencies>
           to local crate to add.

       --registryregistry
           Name of the registry to use. Registry names are defined in Cargoconfigfiles
           <https://doc.rust-lang.org/cargo/reference/config.html>. If not specified, the default registry is
           used, which is defined by the registry.default config key which defaults to crates-io.

   Sectionoptions--dev
           Add as a developmentdependency
           <https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#development-dependencies>.

       --build
           Add as a builddependency
           <https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#build-dependencies>.

       --targettarget
           Add as a dependency to the giventargetplatform
           <https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#platform-specific-dependencies>.

           To avoid unexpected shell expansions, you may use quotes around each target, e.g., --target'cfg(unix)'.

   Dependencyoptions--dry-run
           Don’t actually write the manifest

       --renamenameRename
           <https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#renaming-dependencies-in-cargotoml>
           the dependency.

       --optional
           Mark the dependency as optional
           <https://doc.rust-lang.org/cargo/reference/features.html#optional-dependencies>.

       --no-optional
           Mark the dependency as required
           <https://doc.rust-lang.org/cargo/reference/features.html#optional-dependencies>.

       --public
           Mark the dependency as public.

           The dependency can be referenced in your library’s public API.

           Unstable(nightly-only) <https://doc.rust-lang.org/cargo/reference/unstable.html#public-dependency>

       --no-public
           Mark the dependency as private.

           While you can use the crate in your implementation, it cannot be referenced in your public API.

           Unstable(nightly-only) <https://doc.rust-lang.org/cargo/reference/unstable.html#public-dependency>

       --no-default-features
           Disable the defaultfeatures
           <https://doc.rust-lang.org/cargo/reference/features.html#dependency-features>.

       --default-features
           Re-enable the defaultfeatures
           <https://doc.rust-lang.org/cargo/reference/features.html#dependency-features>.

       -Ffeatures, --featuresfeatures
           Space or comma separated list of featurestoactivate
           <https://doc.rust-lang.org/cargo/reference/features.html#dependency-features>. 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.

   DisplayOptions-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.verboseconfigvalue <https://doc.rust-lang.org/cargo/reference/config.html>.

       -q, --quiet
           Do not print cargo log messages. May also be specified with the term.quietconfigvalue
           <https://doc.rust-lang.org/cargo/reference/config.html>.

       --colorwhen
           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.colorconfigvalue
           <https://doc.rust-lang.org/cargo/reference/config.html>.

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

       -pspec, --packagespec
           Add dependencies to only the specified package.

       --ignore-rust-version
           Ignore rust-version specification in packages.

       --locked
           Asserts that the exact same dependencies and versions are used as when the existing Cargo.lock file
           was originally generated. Cargo will exit with an error when either of the following scenarios
           arises:

           •  The lock file is missing.

           •  Cargo attempted to change the lock file due to a different dependency resolution.

           It may be used in environments where deterministic builds are desired, such as in CI pipelines.

       --offline
           Prevents Cargo from accessing the network for any reason. Without this flag, Cargo will stop with an
           error if it needs to access the network and the network is not available. With this flag, Cargo will
           attempt to proceed without the network if possible.

           Beware that this may result in different dependency resolution than online mode. Cargo will restrict
           itself to crates that are downloaded locally, even if there might be a newer version as indicated in
           the local copy of the index. See the cargo-fetch(1) command to download dependencies before going
           offline.

           May also be specified with the net.offlineconfigvalue
           <https://doc.rust-lang.org/cargo/reference/config.html>.

       --frozen
           Equivalent to specifying both --locked and --offline.

   CommonOptions+toolchain
           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 rustupdocumentation
           <https://rust-lang.github.io/rustup/overrides.html> for more information about how toolchain
           overrides work.

       --configKEY=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-lineoverridessection
           <https://doc.rust-lang.org/cargo/reference/config.html#command-line-overrides> for more information.

       -CPATH
           Changes the current working directory before executing any specified operations. This affects things
           like where cargo looks by default for the project manifest (Cargo.toml), as well as the directories
           searched for discovering .cargo/config.toml, for example. This option must appear before the command
           name, for example cargo-Cpath/to/my-projectbuild.

           This option is only available on the nightlychannel
           <https://doc.rust-lang.org/book/appendix-07-nightly-rust.html> and requires the -Zunstable-options
           flag to enable (see #10098 <https://github.com/rust-lang/cargo/issues/10098>).

       -h, --help
           Prints help information.

       -Zflag
           Unstable (nightly-only) flags to Cargo. Run cargo-Zhelp for details.

cargo(1), cargo-remove(1)

                                                                                                    CARGO-ADD(1)

cargoadd [options] crate…
       cargoadd [options] --pathpathcargoadd [options] --giturl [crate…]