Using Go Modules in everyday life
summary
History shows ~14 competing dependency tools before an official solution; Go Modules become the standard with go.mod and go.sum recording direct requirements and cryptographic hashes, and MVS (minimal version selection) deciding versions. Commands covered: go mod init, go get@version, go mod tidy to remove unused requires, go list -m all, and go mod vendor which copies only used source (it omits tests and some cgo files and can break vendor-based builds). Environment knobs: GOPROXY, GOSUMDB, GOPRIVATE and proxies like Athens and Go Center.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:55Brief History
- 1:35Go Path
- 3:50Go DEP
- 4:24Go Modules
- 4:54MVS
- 6:18New features
- 8:22Environment variables
- 13:32Demo
- 14:20Go Mod File
- 15:27Dependencies
- 18:28Semantic Versioning
- 23:03Go Mod Tidy
- 29:00No Tests
- 29:36Creating a Project
related talks
42mGo Module Hygiene: Keeping go.sum and go.mod in check
29mA History of Dependency Management: 1.0 to Workspaces
15mMulti-Module Repositories
06mLightning Talk: Getting The Most Out Of Go Tool Dependencies
33mHow to Safely and Efficiently Build your App with Modules
17mPackage Management in Go: Under the Hood
07mBuilding A Central Go Modules Repository
24m"Finding Dependable Go Packages"