Module Magic: Multi Module Workspaces to the rescue
summary
Shows how to replace local replace directives with real workspaces so local edits in one module immediately affect dependents: run go work init listing modules, run services from the repo root with go run <module>, and test unpublished or experimental modules without committing or using replace. Workspace creates go.work and go.work.sum, and the workflow avoids fiddly go.mod replaces, simplifies multi-module testing, and warns not to commit go.work to the repo.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:46Go Dependency Management
- 5:51Magic of Modules
- 7:47Dependent Modules
- 8:53Modify Dependent Module
- 10:50Test Dependent Module Approach I
- 13:33Challenges using go modules
- 23:04Getting started with workspaces
- 24:44Add a feature to an upstream module
- 26:22How go work manage dependencies?
- 27:33Experimenting with Unpublished Module
- 30:25Switching between dependency configurations
- 31:36When working with go.work
- 32:26Editor Experience Improvements
- 33:17Benefits Of Workspaces
related talks
38mUsing Go Modules in everyday life
08mFederated modules and Monorepo
25mManaging Workspaces With the TFE Provider
46mExploring the power of monorepos: When and why to use them
06mHow I Learned to Stop Worrying and Love the Mono Repo
29mMonorepos, are they right for you?
01h 00mHow to Build Modularity with SPM and a Monorepo Without Going Gray
24mBuilding your ideal codebase: monorepos & multirepos living in harmony