47

I'm trying to get a good understanding of Go modules and am a bit puzzled by the difference between the go get command and the go mod download command.

"The go get command updates module dependencies in the go.mod file for the main module, then builds and installs packages listed on the command line." https://golang.org/ref/mod#go-get

Whereas the Go mod download is described as :

"The go mod download command downloads the named modules into the module cache. " https://golang.org/ref/mod#go-mod-download

Clearly go get performs some dependency management which go mod download does not, but what is the difference between installing packages with go get and downloading modules to the module cache in go mod download.

JJ_programmer
  • 492
  • 1
  • 4
  • 6
  • 2
    like the quoted section says, `go get` updates `go.mod`. Also see that using `go get` to build and install is deprecated: https://golang.org/doc/go1.16#go-command – JimB Feb 24 '21 at 17:41

1 Answers1

66

Your module's go.mod file records which versions of dependencies it requires. The source code for those dependencies is stored in a local cache.

go get updates the requirements listed in your go.mod file. It also ensures that those requirements are self-consistent, and adds new requirements as needed so that every package imported by the packages you named on the command line is provided by some module in your requirements.

As a side-effect of updating and adding requirements, go get also downloads the modules containing the named packages (and their dependencies) to the local module cache.

In contrast, go mod download does not add new requirements or update existing requirements. (At most, it will ensure that the existing requirements are self-consistent, which can occur if you have hand-edited the go.mod file.) It only downloads either the specific module versions you've requested (if you requested specific versions), or the versions of modules that appear in your requirements.

bcmills
  • 4,391
  • 24
  • 34