That has the tendency of breaking Gomock ( issue) which were unknowingly not using vendor/ before 1.14. The vendor/ is picked up automatically.Note that some slight changes in behaviors unrelated to GO111MODULE happened: The GO111MODULE variable has the same behavior as with Go 1.13. behaves like GO111MODULE=off in the GOPATH with no go.mod.So you can keep all your repositories in your GOPATH with Go 1.13. behaves like GO111MODULE=on anywhere there is a go.mod OR anywhere outside the GOPATH even if there is no go.mod.Using Go 1.13, GO111MODULE’s default ( auto) changes: Whenever you are in your GOPATH and you want to do an operation that requires Go modules (e.g., go get a specific version of a binary), you need to do: similarly to GO111MODULE=off when you are inside the GOPATH even if a go.mod is present.similarly to GO111MODULE=on when you are outside of GOPATH,.GO111MODULE=off forces Go to behave the GOPATH way, even outside of GOPATH. GO111MODULE=on will force using Go modules even if the project is in your GOPATH. One of the first pain-points is that depending on the Go version, its semantics change. GO111MODULE is an environment variable that can be set when using go for changing how Go imports packages. One environment variable is responsible for 95% of this pain: GO111MODULE. Since then, the interaction between the ‘GOPATH behavior’ and the ‘Go Modules behavior’ has become one of the biggest gotchas of Go. Instead of using the GOPATH for storing a single git checkout of every package, Go Modules stores tagged versions with go.mod keeping track of each package’s version.

Go Modules (previously called vgo – versioned Go) were introduced with Go 1.11. There was no versioning and the ‘master’ branch would represent a stable version of the package.

Instead, go get would fetch all the sources by using their import paths and store them in $GOPATH/src. When Go was first introduced in 2009, it was not shipped with a package manager. Set GO111MODULE on a per-folder basis with direnvįirst off, let’s talk about GOPATH.Where are the sources of the dependencies with Go Modules.Remember that go get also updates your go.mod.

The pitfall of go.mod being silently updated.

Installing binaries with GO111MODULE=on go get is deprecated.

Faster downloading of dependencies if you are using Git to fetch modules.

Go install this short post, I will explain why GO111MODULE was introduced in Go 1.11, its caveats and interesting bits that you need to know when dealing with Go Modules.

Check go path mac