Long term success of your Angular projects with automated architecture validation!
summary
Shows how to use the ESLINT boundaries plugin to encode architecture by file paths so the tool captures feature name and app name variables, then enforces rules that block core importing lazy features and prevent cross-feature imports. Rules run live in the editor and in CI, use a strict mode that forces every source file to belong to a type (with an ignore list for exceptions), work in a single Angular CLI workspace with apps and libraries, and can be adopted gradually on an existing codebase.
AI-written summary · about
chapters (10)
- 0:00Why architecture matters
- 3:15About the speaker and Angular expertise
- 7:13Architectural decay symptoms
- 10:43Automated validation with ESLint
- 14:57ESLint plugin boundaries
- 22:44Multi-project workspace rules
- 25:56Library validation rules
- 29:08Gradual adoption tips
- 32:39Balancing rules and productivity
- 33:23Resources and closing
related talks
41mLong term success of your Angular projects
29mCustom ESLint Rules with Angular Schematics
01h 03mThe best way to Architect Your Angular Libraries
35mHow to Organize an Angular Project
28mAngular in a microservices world
21mSustainable Angular Architecture
25mAngular at Large Organizations
01h 01mDomain-Driven Design and Angular