Go Modules- A Guide for monorepos (Part 1)

This post details the initial challenges and solutions for adopting Go modules in a multi-module monorepo, focusing on the transition from the 'vendor' directory to Go modules. It covers the initial obstacles with manual vendoring, the adoption of Glide, and the subsequent switch to `go mod vendor`. Key issues addressed include handling incompatible dependencies, the 'module cannot contain other modules' rule, dependency inheritance, and implicit updates to the `go.mod` file. The post also highlights the utility of `go mod graph` for dependency tracing.