go-modules

go mod download is downloading all of the modules in the dependency graph, which it can determine from reading only the go.mod files. It doesn’t know which of those modules are actually needed to satisfy a build, so it doesn’t pull in the checksums for those modules (because they may not be relevant). On the … Read more

The go.mod file should be at the root of your project (in this case, my-api-server/go.mod). The first part of the module path should be a domain/path. For example, the full path might be github.com/your-github-username/my-api-server. The error you’re seeing is because the first part is not a domain (with a period). You don’t have to publish … Read more

You can run go clean -modcache and then go mod tidy which will re-download all deps with the correct checksum (this updates the pkg cache in $GOPATH/pkg/mod/). To update vendor/ folder run: go mod vendor.

Because in Go 1.17 the module graph has been changed to enable pruning and lazy loading. The second require block contains indirect dependencies. https://golang.org/doc/go1.17#go-command If a module specifies go 1.17 or higher, the module graph includes only the immediate dependencies of other go 1.17 modules, not their full transitive dependencies. […] […] If a module … Read more

It was an issue #26610, which is fixed now. So now you can just use: go mod download For this to work you need just the go.mod / go.sum files. For example, here’s how to have a cached multistage Docker build: (source) FROM golang:1.17-alpine as builder RUN apk –no-cache add ca-certificates git WORKDIR /build # … Read more

The easiest and working out-of-the-box solution is to put your database package / module into a VCS (e.g. github.com), so other packages (inside other modules) can simply refer to it by importing it like: import “github.com/someone/database” If you do so, you don’t even have to fiddle with the go.mod files manually, everything will be taken … Read more

Go Modules takes care of versioning, but it doesn’t necessarily take care of modules disappearing off the Internet or the Internet not being available. If a module is not available, the code cannot be built. Go Proxy will mitigate disappearing modules to some extent by mirroring modules, but it may not do it for all … Read more

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 … Read more