cargo-remove — Remove dependencies from a Cargo.toml manifest file

Description

       Remove one or more dependencies from a Cargo.toml manifest.

Environment

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

Examples

        1. Remove regex as a dependency

               cargo remove regex

        2. Remove trybuild as a dev-dependency

               cargo remove --dev trybuild

        3. Remove nom from the x86_64-pc-windows-gnu dependencies table

               cargo remove --target x86_64-pc-windows-gnu nom

Exit Status

       •  0: Cargo succeeded.

       •  101: Cargo failed to complete.

Name

       cargo-remove — Remove dependencies from a Cargo.toml manifest file

Options

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

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

--targettarget
Remove 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)'.

MiscellaneousOptions--dry-run
Don’t actually write to the manifest.

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.

--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.

--lockfile-pathPATH
Changes the path of the lockfile from the default (<workspace_root>/Cargo.lock) to PATH. PATH must
end with Cargo.lock (e.g. --lockfile-path/tmp/temporary-lockfile/Cargo.lock). Note that providing
--lockfile-path will ignore existing lockfile at the default path, and instead will either use the
lockfile from PATH, or write a new lockfile into the provided PATH if it doesn’t exist. This flag can
be used to run most commands in read-only directories, writing lockfile into the provided PATH.

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 #14421 <https://github.com/rust-lang/cargo/issues/14421>).

PackageSelection-pspec…, --packagespec…
Package to remove from.

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.