Closed
Description
Actually, I'm not sure if it should be go mod mvs
, some different subcommand, or rolled into something like go mod why
. But, what I'd like is something like:
$ go mod graph
cloud.google.com/go go.opencensus.io@v0.21.0
cloud.google.com/go github.com/foo/bar@v0.0.1
cloud.google.com/go google.golang.org/api@v0.4.0
google.golang.org/api@v0.4.0 go.opencensus.io@v0.22.0
github.com/foo/bar go.opencensus.io@v0.17.3
$ go mod mvs
go.opencensus.io@v0.22.0
go.opencensus.io@v0.22.0
go.opencensus.io@v0.21.0
go.opencensus.io@v0.17.3
github.com/foo/bar@v0.0.1
github.com/foo/bar@v0.0.1
google.golang.org/api@v0.4.0
google.golang.org/api@v0.4.0
I'm also not sure what the exact output should be. The above's output isn't great because it's not easily combined with things like go mod graph
. Basically, I'm reaching for a way to get an explanation of which versions of modules were actually picked, and why they were picked.