Git submodules: we have monorepo at home
summary
Argues that git submodules let small teams get monorepo-like benefits without full monorepo tooling by embedding shared repos as directories, using commands like git submodule add <url> and git submodule update --init and per-project submodule branches to avoid forced updates. Uses Next.js, TypeScript, Apollo and Storybook examples, integrates linting/tests into the app build, and reports almost a year of production use that reduced duplicated fixes and lets CI build once for app+shared code.
AI-written summary · about
chapters (19)
- 0:00intro
- 0:22preamble
- 2:24about vadim
- 2:39about etg
- 4:00how to do it once and forget?
- 4:20monorepository
- 5:28tools
- 5:45bus factor = 1
- 6:18polyrepository and packages
- 7:28broken the loop? how to test reusable code?
- 8:46_app.tsx + apollo client + generic getinitialprops = ?
- 9:56git submodules
- 11:59teach me
- 16:30tips and tricks / trade off
- 17:28common functionality should have common text translations
- 18:40abstract, parameterize, minimize
- 19:03collaboration is good
- 19:54document the questions
- 21:02thank you
related talks
29mModularity and Monorepositories
24mBuilding your ideal codebase: monorepos & multirepos living in harmony
46mExploring the power of monorepos: When and why to use them
41mHandling Monorepos Today
31mSubito’s journey to a scalable monorepo
05mJonathan Eskew - SeattleJS Conference
31mMonoRepos for the Masses
06mHow I Learned to Stop Worrying and Love the Mono Repo