Mastering the Monorepo: How NX Schematics Transformed Our 80+ Angular Projects!
summary
Claims managing 80+ Angular projects becomes a two-workspace setup that cuts months of manual updates to hours by using NX generators, an NX plugin that adds a rename executor, and npm/bash orchestration to create apps with stripped chapter names. The repo ships a shared global.scss and Tailwind setup via a UI library, and a migration called replace app toolbar programmatically swaps hardcoded headers and the old Angular logo across start and final workspaces.
AI-written summary · about
chapters (15)
- 0:00Mastering monorepos with NX
- 1:0880 Angular projects challenge
- 3:35Angular Cookbook case study
- 5:21NX workspaces simplified projects
- 7:07NX plugins for naming conflicts
- 9:16NX plugin for renaming apps
- 12:27Streamlining project creation
- 14:31Consistent UI with libraries
- 17:18Global styles and Tailwind CSS
- 19:43Disaster recovery with Angular 17
- 21:51NX migrations for updates
- 24:18NX migrations automation
- 26:05NX impact on 80 projects
- 27:12Resources and codebase
- 29:06Q&A
related talks
42mRefactoring 80+ Angular projects and what went wrong
33mRefactoring 80+ Angular projects and what went wrong
28mConsolidate, Enhance, Scale: End-to-End Angular Monorepo Management with Nx
09mUsing Nx: Angular CLI Power-ups for Modern Development
29mSupercharging the Angular CLI with Nx
36mHow to scale up your angular projects like a pro
01h 03mMonorepo – How to do frontend faster, better and safer
24mBuilding Fast, Maintainable JavaScript Monorepos with Nx