Building your ideal codebase: monorepos & multirepos living in harmony
summary
Presents a pragmatic hybrid repo strategy: use a monorepo per application plus a separate shared monorepo for libraries to get isolation and reuse while preventing cross-imports. Describes tooling and practices including Lerna, Yarn workspaces, manual linking, publishing modules via package.json, CI/local hoisting that cut install times from 40 to 7 minutes, migration steps, common failure modes (e.g., duplicate React breaking styles), and the rule that changing one app must never break another.
AI-written summary · about
chapters (13)
- 0:00Welcome
- 1:00Monorepo vs multirepo
- 2:44Multirepo frictions
- 4:50Monorepo pros and cons
- 6:56Key monorepo tools
- 7:38Monorepo best practices
- 9:26Medal app suite case
- 12:38Scaling monorepo problems
- 15:51Yarn dependency hosting
- 17:58Fixing monorepo fragility
- 19:44Scalable monorepo requirements
- 21:51Team vs suite monorepo
- 22:57Conclusion
