Migrating from Dep to Go Modules is very easy. Run go version and make sure you’re using Go version 1.11 or later. Move your code outside of GOPATH or set export GO111MODULE=on. go mod init [module path]: This will import dependencies from Gopkg.lock. go mod tidy: This will remove unnecessary imports, and add indirect ones. … Read more
I generally use go get and go mod tidy for same. It works all the time. go mod tidy
Found it https://go.dev/blog/using-go-modules#removing-unused-dependencies go mod tidy So basically, once the package is not being imported in any package you can perform a go mod tidy and it will safely remove the unused dependencies. And if you are vendoring the dependencies, then run the command below to make the module changes be applied in the vendor … Read more
Module structure The most common and easiest approach is: Use a single go.mod per repository, and Place the single go.mod file in the repository root, and Use the repository name as the module path declared in the module line in the go.mod (If you are using a custom import path such as me.io/mymod rather than … Read more
Command go: Edit go.mod from tools or scripts: Usage: go mod edit [editing flags] [go.mod] Edit provides a command-line interface for editing go.mod, for use primarily by tools or scripts. It reads only go.mod; it does not look up information about the modules involved. By default, edit reads and writes the go.mod file of the … Read more
Accepted answer is correct, but really not friendly for me who just get in touch with go module. I made some investigation base on the answer & make a conclusion base on this as next, in case anyone needed: Standard commands like go build or go test will automatically add new dependencies as needed to … Read more
tl;dr; this is what you want: go get -u go mod tidy and to recursively update packages in any subdirectories: go get -u ./… The inconsistencies you are seeing is due to the inherent organic nature of software. Using your example, commit d24acdbf of git://github.com/walles/moar most likely was checked in by the maintainer without running … Read more
Short Answer: go env -w GOPRIVATE=github.com/repoURL/private-repo OR If you want to allow all private repos from your organization go env -w GOPRIVATE=github.com/<OrgNameHere>/* Long Answer: Check “Module configuration for non-public modules” for more information: The GOPRIVATE environment variable controls which modules the go command considers to be private (not available publicly) and should therefore not use … Read more
It seems the issue has nothing to do with Buffalo and more with my lack of understanding of Go in general. running go mod tidy solved the issue This command goes through the go.mod file to resolve dependencies: delete the packages that are not needed download those needed update the go.sum I am still unsure … Read more