depth issues

Can show the dependencies version?

2

this repo is very good! thanks! And , can show the dependencies version?

Log error message

Error logging helps to track down issues. For example, I was investigating why swaggo failed in my project and found the `package name is not in GOROOT` error after I...

nodivbyzero

Possible performance issue detected in downstream library using `depth`

3

Hi @KyleBanks, An issue has been reported recently in a downstream tool, [swaggo/swag](https://github.com/swaggo/swag), which uses `depth` to calculate required dependencies in order to build valid OpenAPI 2.0 output as a...

magandrez

graphviz intergration

5

- adding the ability to render the dependency graph using graphviz with `-graph` flag

Niraj-Fonseka

"depth" does not seem to work on any packages other than "depth"

8

``` [~] % depth github.com/KyleBanks/conways-gol 'github.com/KyleBanks/conways-gol': FATAL: unable to resolve root package [~]!% depth github.com/KyleBanks/goggles 'github.com/KyleBanks/goggles': FATAL: unable to resolve root package ``` It doesn't work on any KyleBanks packages...

iphydf

Update output in README

1

I've updated depth's output in README. I think the result depends on the version of golang and this project seems to support go1.9, so I used go1.9.

ksoichiro

Does it work for package 'main'?

2

I tried this on a server program where I want to see the dependency tree starting from the main package. I cd'ed into the same directory where main.go is found...

webern

If local Go is different version than Go used to compile `depth`, `tree.Resolve` fails with an unhelpful error message

Hi there! We've been using `depth` as a library as a part of https://github.com/fossas/fossa-cli to power our Go dependency discovery. We recently ran into an interesting bug where using a...

elldritch