cargo-tree 0.1.0

A Cargo subcommand that visualizes a crate's dependency graph in a tree-like format
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57

# cargo-tree

[![Build Status](https://travis-ci.org/sfackler/cargo-tree.svg?branch=master)](https://travis-ci.org/sfackler/cargo-tree)

`cargo tree` is a Cargo subcommand that visualizes a crate's dependency graph
in a tree-like format.

In its default mode, `cargo tree` will print the dependency graph from the
local crate outwards:

```
$ cargo tree
chrono v0.2.17 (file:///Volumes/git/rust/rust-chrono)
├── num v0.1.29
│  ├── rand v0.3.12
│  │  ├── advapi32-sys v0.1.2
│  │  │  ├── winapi v0.2.5
│  │  │  └── winapi-build v0.1.1
│  │  ├── libc v0.2.4
│  │  └── winapi v0.2.5 (*)
│  └── rustc-serialize v0.3.16
├── rustc-serialize v0.3.16 (*)
├── serde v0.6.6
│  └── num v0.1.29 (*)
├── serde_json v0.6.0
│  ├── num v0.1.29 (*)
│  └── serde v0.6.6 (*)
└── time v0.1.34
   ├── kernel32-sys v0.2.1
   │  ├── winapi v0.2.5 (*)
   │  └── winapi-build v0.1.1 (*)
   ├── libc v0.2.4 (*)
   └── winapi v0.2.5 (*)
```

Crates will only have their dependencies displayed the first time they are
shown - further copies will have a `(*)` appended to indicate that their output
has been truncated.

`cargo tree` can also operate in an "inverse" mode where the dependency tree is
walked backwards. This is most often useful when trying to determine where
a certain crate is coming from:

```
cargo tree -p libc -i
libc v0.2.4
├── rand v0.3.12
│  └── num v0.1.29
│     ├── chrono v0.2.17 (file:///Volumes/git/rust/rust-chrono)
│     ├── serde v0.6.6
│     │  ├── chrono v0.2.17 (file:///Volumes/git/rust/rust-chrono) (*)
│     │  └── serde_json v0.6.0
│     │     └── chrono v0.2.17 (file:///Volumes/git/rust/rust-chrono) (*)
│     └── serde_json v0.6.0 (*)
└── time v0.1.34
   └── chrono v0.2.17 (file:///Volumes/git/rust/rust-chrono) (*)
```