Angular Monorepo Diaries

on YouTube ↗34m

" summary

Claims a single repository hosts multiple Angular applications and shared libraries, uses Angular CLI plus a dependency-graph build tool to run only affected tests and parallel builds, and uses Lerna to manage many package.jsons. A SpaceX demo app plus a GraphQL backend proves the pattern; about 25 engineers in 3–4 person teams share ~dozens (potentially hundreds) of libraries. Outcomes: fewer inconsistent internal npm versions, CI times drop when using the graph tool, but upfront rules and ongoing code-review demos remain essential.

AI-written summary · about

" chapters (7)

1. 0:00Start
2. 2:03Books to read
3. 7:03Why monorepo?
4. 12:49How does the monorepo help us?
5. 13:22Demo application
6. 15:52Wait, what is different
7. 27:55Think differently

" related talks

• 01h 00mUsing Monorepos for Scalable AppsJames Henry, Dylan Johnson, Mike Haas · ng-conf 2019
• 30mAngular in a Microservices WorldKwinten Pisman · NG-BE 2018
• 33mArchitectures for huge Angular based Enterprise Applications: npm Packages, Monorepos and MicroservicesManfred Steyer · DevOne 2019
• 31mArchitectures for huge Angular based enterprise applications npm Packages, Monorepos and Micro AppsManfred Steyer · Angular Connect 2018
• 22mSustainable Angular Architectures with Monorepos and Strategic Domain Driven DesignManfred Steyer · NG Poland 2020
• 35mHow to Organize an Angular ProjectSergio Brito · Connect.Tech 2021
• 28mAngular in a microservices worldKwinten Pisman · ngVikings 2019
• 46mExploring the power of monorepos: When and why to use themSteve Lam, Jason Hong La · XConf Lite APAC 2024 - Vietnam