cargo-visualize
| Crates.io | cargo-visualize |
| lib.rs | cargo-visualize |
| version | |
| source | src |
| created_at | 2025-03-11 04:25:09.627923+00 |
| updated_at | 2025-04-12 10:59:59.021246+00 |
| description | Interactive cargo dependency graph visualization |
| homepage | |
| repository | https://github.com/kxxt/cargo-visualize |
| max_upload_size | |
| id | 1587527 |
| Cargo.toml error: | TOML parse error at line 26, column 1 | 26 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
| size | 0 |
Levi Zim (kxxt)
documentation
README
cargo-visualize
Know your dependencies via interactive cargo dependency graph visualization.
An opinionated fork of cargo-depgraph that focuses on interactivity.
🚧 Under Development 🚧
cargo-visualizeis still under heavy development. Missing features and frictions with the UI interface are expected. You are welcome to submit pull requests to makecargo-visualizebetter!
Installation
Usage
cargo visualize [options]
The full list of options can be seen by running
cargo visualize --help
Commonly useful options:
--all-deps--all-deps --dedup-transitive-deps
Output explanation
- Cyan background = root / workspace member
- Grey background = target-specific dependency
- Green background = optional dependency
- Dark Green background = optional target-specific dependency
- Dotted lines = optional dependency (could be removed by disabling a cargo feature)
- Dashed lines = transitively optional dependency (could be removed by removing one of the dotted edges)
Advanced Usage
The G6 Graph engine is exposed as a global variable.
You can interact with the graph variable directly in F12 Developer Console.
However, we make no promise about the stability of this interface.