Angular performance pitfalls and how to avoid them
summary
Describes concrete fixes: enable build optimizer and strip template whitespace to shrink bundles, replace getters/classes/async/await when they transpile into large ES5 boilerplate, attach heavy listeners with runOutsideAngular to avoid repeated change detection, and render menus as templates instead of hidden DOM. Shows test-speed wins: compile only the needed component (reduces test build time by 60%) and prefer fakeAsync over async to make tests deterministic and faster.
AI-written summary · about
chapters (3)
related talks
31mAngular Performance: Your App at the Speed of Light
43mAngular Performance Workshop
22mThe dark side of tuning Angular performance
34mHigh-Performance Applications with Angular
20mTools for Fast Angular Applications
19mAngular Performance Patterns
23mPerformance optimizations in Angular
31mOptimized Angular apps: smaller, faster, better