/ go Public
cmd/go: "mod why" should show all the paths to a package or module #41305
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
This label describes issues relating to any tools in the x/tools repository.
It would be nicer if
go mod whygave all the paths to a package or module, not just the shortest path. This would help answer common questions like "what would it take to remove dependency X?".
I can get that information indirectly via
go list -deps -jsonor
go mod graph, processing or plotting the output somehow. Or even using third party tools like https://github.com/loov/goda.
Still, I think this rather simple change would make
go mod whysignificantly more useful for simple use cases, without having to go to something much more involved like a graph or a dependency query language.
The text was updated successfully, but these errors were encountered: