CARGO-REMOVE(1)

📦 version 1.95.0, in ubuntu stonking

CARGO-REMOVE 💅✨

okay bestie, this is the page for cargo-remove from the General Commands Manual — it's the little command that rips dependencies OUT of your Cargo.toml like it's clearing out a toxic situationship 🫶

✨ NAME ✨

cargo-remove — remove dependencies from a Cargo.toml manifest file, no cap 🎀

🌸 SYNOPSIS 🌸

cargo remove [options] dependency…

🦋 DESCRIPTION 🦋

It removes one or more dependencies from a Cargo.toml manifest. That's it, that's the whole vibe. Say goodbye, block them, move on 💖

👑 OPTIONS 👑

🎀 Section options 🎀

These tell cargo which little section of your manifest the dependency is living in, so it knows where to go snatch it from.

lowkey important: to avoid unexpected shell expansions, you may put quotes around each target, like --target 'cfg(unix)'. do that fr fr 🙈

🍓 Miscellaneous Options 🍓

  • --dry-run — doesn't actually write to the manifest. it's giving "rehearsal only", nothing gets touched 💀

🌈 Display Options 🌈

  • -v, --verbose — use verbose output. may be specified twice for "very verbose" output, which includes extra output like dependency warnings and build script output. may also be specified with the term.verbose config value — <https://doc.rust-lang.org/cargo/reference/config.html>.
  • -q, --quiet — do not print cargo log messages. may also be specified with the term.quiet config value — <https://doc.rust-lang.org/cargo/reference/config.html>.
  • --color when — control when colored output is used. the valid values are, and I'm obsessed with all of them:
    • 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 — <https://doc.rust-lang.org/cargo/reference/config.html>.

🧚 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. main character energy, it goes looking 🔥
  • --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 these 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. very "we do not improvise here" of it 💅

  • --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, bestie: 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.offline config value — <https://doc.rust-lang.org/cargo/reference/config.html>.

  • --frozen — equivalent to specifying both --locked and --offline. two-for-one deal, slay ✨

💜 Package Selection 💜

  • -p spec…, --package spec… — package to remove from. pick your target, bestie 🎯

⭐ Common Options ⭐

  • +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 rustup documentation at <https://rust-lang.github.io/rustup/overrides.html> 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 at <https://doc.rust-lang.org/cargo/reference/config.html#command-line-overrides> for more information.
  • -C PATH — 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 -C path/to/my-project build.
🌙 this option is only available on the nightly channel — <https://doc.rust-lang.org/book/appendix-07-nightly-rust.html> — and requires the -Z unstable-options flag to enable (see #10098 at <https://github.com/rust-lang/cargo/issues/10098>). so like, not for everyone yet 😭
  • -h, --help — prints help information. the classic, the icon 👑
  • -Z flag — unstable (nightly-only) flags to Cargo. run cargo -Z help for details.

🌱 ENVIRONMENT 🌱

See the reference at <https://doc.rust-lang.org/cargo/reference/environment-variables.html> for details on environment variables that Cargo reads. yes, Cargo is nosy like that 🙈

💀 EXIT STATUS 💀

  1. 0: Cargo succeeded. ate. 💅
  2. 101: Cargo failed to complete. not the vibe. 😭

🎀 EXAMPLES 🎀

  1. Remove regex as a dependency
cargo remove regex
  1. Remove trybuild as a dev-dependency
cargo remove --dev trybuild
  1. Remove nom from the wasm32-unknown-unknown dependencies table
cargo remove --target wasm32-unknown-unknown nom

🌸 SEE ALSO 🌸

cargo(1), cargo-add(1) — go read those too, bestie, they're the sibling energy 🫶

okay that's the whole page!! mwah 💖 this was cargo-remove(1) from the General Commands Manual, and if you ever need the source-of-truth version it lives right there under that same name and section. bye bestie, go clean up your manifest ✨🎀🦋

📦 where this page comes from