One Codebase to Rule Them All: A Monorepo Journey
summary
Migrating ~50 separate repositories holding ~120 components into one monorepo unifies versions and cuts dependency headaches but introduces build and merge complexity. The team uses NX plus semantic release with caching and affected commands, a phased migration taking ~3 months with seven developers, and parallelized CI to drop a dropdown-package build from ~90 minutes to ~18–20 minutes. Claims: single-versioning, easier refactors, more merge conflicts; tradeoffs documented with concrete numbers and tooling.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:26Multi-repo vs monorepo
- 3:14Kendo UI Angular challenges
- 5:042016 multi-repo reasons
- 7:57Scattered dependencies problems
- 11:54Team frustration and migration
- 13:18Monorepo migration tools
- 16:08Phased migration plan
- 17:56Monorepo benefits
- 20:07New monorepo challenges
- 21:16NX caching for builds
- 23:28Parallel builds
- 25:20Merge conflicts and strategies
- 28:11Unified versioning trade-offs
- 31:55When to use monorepo
- 32:40Key takeaways
- 34:52Q&A
- 35:13Code search tools
- 37:00Parallel pipelines
- 37:26Team feedback
- 37:51Code ownership
related talks
01h 00mUsing Monorepos for Scalable Apps
31mThe monorepo: self-organising codebases and automatic scaling
01h 03mMonorepo – How to do frontend faster, better and safer
46mExploring the power of monorepos: When and why to use them
19mEscaping Chaos: Strategies to Move from Polyrepo to Monorepo
28mConsolidate, Enhance, Scale: End-to-End Angular Monorepo Management with Nx
24mBuilding your ideal codebase: monorepos & multirepos living in harmony
45mMonorepos - The Benefits, Challenges and Importance of Tooling Support