What dependency fields might be relevant to indicate?

[epage]

As of #18, we dim optional dependencies.

What else might we want to show, and how?

• public?

[epage]

From #22 (more appropriate home here)

If its not terrible to do, I think we should prefer relative paths, rather than absolute paths.

I also wonder if we should reserve showing all dependencies for a --verbose. Maybe we only show public dependencies by default? Its still an unstable feature but something for us to keep in mind as we work to stabilize both of these.

[epage]

I also wonder if we should reserve showing all dependencies for a --verbose. Maybe we only show public dependencies by default?

How about we show all the dependencies and only show the dev-dependencies and build-dependencies for a --verbose. I guess checking its dependencies before you use it in your project would always be considered.

[epage]

Run cargo info cargo

My concern is we are showing too much and we need to find a way to filter things down. Dependencies are mostly an implementation detail (except public) but people sometimes care, so I figure that holding off on private dependencies to --verbose might buy us more space.