cargo-tree

cargo-tree copied to clipboard

Identify proc_macro dependencies

1

When cross-compiling, it's useful to know which crates are compiled for the host and which for the target. The `[build-dependencies]` and `[dev-dependencies]` sections are already useful for filtering some of...

jethrogb

Feature request: print features used to build each crate in tree

3

Thanks for this tool, to debug issue like desribed at rust-lang/cargo#4323 it would be nice to show in `cargo tree` output the features used for building each crate (it can...

Dushistov

Add JSON output capabilities

3

I needed this to be able to output JSON for parsing elsewhere.

Twey

Similar to the `--no-dev-dependencies` option, it would be useful to be able to filter out build dependencies.

fabricedesre

I tried running cargo-tree on my workspace's top level crate: ``` > cargo tree -i -p fs2 error: There are multiple `fs2` packages in your project, and the specification `fs2`...

Boscop

Add a --all-features-recursive option and communicate better about omitted features

1

Currently, `cargo-tree --all-features` only resolves the features of the top-level crate and their dependencies, which may omit features from child crates. For example, chrono-0.4.0 depends on num 0.1 with default-features...

infinity0

Please support running standalone

4

cargo-tree expects to find a local Cargo.toml file. Please consider adding support for running on a named package directly from the registry: `cargo tree somecrate`.

joshtriplett