From bfa9eca33c819f1b6df607bdf1de02bfbfeb17ae Mon Sep 17 00:00:00 2001 From: thepudds <20628140+thepudds@users.noreply.github.com> Date: Fri, 7 Dec 2018 12:53:41 -0500 Subject: [PATCH] minor tweaks to recent material --- Modules.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Modules.md b/Modules.md index c1e4802d..72536bf3 100644 --- a/Modules.md +++ b/Modules.md @@ -878,7 +878,7 @@ Please see the question "Won't minimal version selection keep developers from ge 2. The second step usually should be to check `go list -m all` to see the list of actual versions selected for your build. `go list -m all` shows you the final selected versions, including for indirect dependencies and after resolving versions for any shared dependencies. It also shows the outcome of any `replace` and `exclude` directives. -3. A good next step can be to examine the output of `go mod graph` or `go mod graph | grep `. `go mod graph` prints the module requirement graph (including taking into account replacements). Each line in the output has two fields: the first column is a consuming module, and the second column is one of that module's requirements (including the version required by that consuming module). This can be a quick way to see which modules are requiring a particular dependency, including when you different versions required for shared dependencies. +3. A good next step can be to examine the output of `go mod graph` or `go mod graph | grep `. `go mod graph` prints the module requirement graph (including taking into account replacements). Each line in the output has two fields: the first column is a consuming module, and the second column is one of that module's requirements (including the version required by that consuming module). This can be a quick way to see which modules are requiring a particular dependency, including when your build has different version numbers required for shared dependencies. `go mod why -m ` can also be useful here, although it is typically more useful for seeing why a dependency is included at all (rather than why a dependency ends up with a particular version).