Long term success of your Angular projects
summary
Shows a concrete, working approach: an ESLint plug-in boundaries setup plus the TypeScript import resolver that enforces core vs feature rules by file-path patterns, auto-blocks forbidden imports in editor and CI, and is iteratively adoptable for legacy code. Claims an enterprise deployment across projects with 220 SPAs and 30 libraries, explains capture variables for apps/features, and demonstrates that automated architecture validation prevents circular imports and preserves lazy-loading and isolation.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:57Architecture in Angular projects
- 9:59Automated validation with ESLint
- 21:58ESLint plugin boundaries
- 28:00Multi-project setups
- 31:15Strictness and granularity
- 35:27Architecture recommendations
- 36:56Q&A
related talks
37mLong term success of your Angular projects with automated architecture validation!
28mAngular in a microservices world
22mCommon Challenges Facing Angular Enterprises
31mArchitectures for huge Angular based enterprise applications npm Packages, Monorepos and Micro Apps
35mHow to Organize an Angular Project
29mCustom ESLint Rules with Angular Schematics
25mAngular at Large Organizations
19mTuning Your Angular Application