Jonathan Eskew - SeattleJS Conference
summary
Monorepos let teams keep related packages in one repository so multiple modules change, test, and release together without juggling multiple git repos, and the claim is that this reduces coordination friction and support overhead for projects with many packages. Node and NPM ecosystems benefit from tools like lerna.js which links dependencies across packages, manages publishing and commits, and preserves semantic versioning. Large shops like Google and Facebook use the pattern, and it cuts issue noise for projects publishing 100 libraries.
AI-written summary · about
related talks
29mModularity and Monorepositories
46mExploring the power of monorepos: When and why to use them
24mBuilding your ideal codebase: monorepos & multirepos living in harmony
34mAngular Monorepo Diaries
19mMonorepos: Any Size Fits All
19mKeynote: Why Monorepos
31mMonoRepos for the Masses
29mMonorepos, are they right for you?