Engineering Scalable Angular Components
summary
Concrete claims and patterns for making Angular components shrinkable and optional: use providedIn: 'root' so services become tree‑shakeable; move rare features into optional directives that bind alternate implementations via an injection token with forwardRef so unused directives disappear; implement features like table sorting with push and pull directive patterns (directive pushes callbacks or component optionally injects directive) and be aware webpack only splits at ES module entry points and Ivy moves templates into component classes.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:14What I Mean by Scalable Components
- 5:13Iv Rendering Engine
- 8:26When Do these Considerations Actually Matter
- 10:02Tree Shakeable Services
- 16:02Data Table Component
- 16:39Push and Pull Approaches
- 16:57Push-Based Approach
related talks
32mLightweight Architectures with Angular's Latest Innovations
30mAngular: Keeping it Fat, Dumb, and Happy: An Architectural Approach
54mBuilding Fast Angular Applications by Default
23mTree-shakable Components and Optional NgModules
34mScalable Angular Architecture
26mScalable Angular Architecture
18mLightweight Architectures with Angular's Latest Innovations
27mThe good, the bad and the ugly - Component architecture at scale