Keynote: Why Monorepos
summary
Monorepos reduce duplication and speed integration by keeping related apps and libraries in one repo, using tools like nx, lerna or turborepo (and Bazel inspiration) to run delta-based builds and computation caching so CI only rebuilds affected projects. A single version policy enforces shared dependency versions to avoid version skew. Examples show a UI button unified instead of ten copies and bug fixes landing immediately across apps rather than waiting weeks.
AI-written summary · about
chapters (10)
- 0:00Introduction to monorepos
- 1:01History of code organization
- 3:09Shift to polyrepos
- 8:04Problems with polyrepos
- 8:45Return to structured monorepos
- 9:48Tooling for monorepos
- 12:36Monorepo examples
- 15:48Single version policy
- 16:51Bug fixing in monorepos vs polyrepos
- 18:39Conclusion and resources
related talks
19mKeynote: Why Monorepos
46mExploring the power of monorepos: When and why to use them
29mUnderstanding Monorepos: What you need to know
24mBuilding your ideal codebase: monorepos & multirepos living in harmony
29mMonorepos, are they right for you?
31mThe monorepo: self-organising codebases and automatic scaling
19mMonorepos: Any Size Fits All
01h 03mMonorepo – How to do frontend faster, better and safer