Bad Practices, what NOT to do in Angular
summary
Concrete anti-patterns and fixes: measuring bundle size with a bundle analyzer and adding the build optimizer gives a small but real reduction; replacing manual unsubscribe patterns and takeWhile with takeUntil or the async pipe removes leaks; avoid parent callers invoking child methods — prefer input-driven components so trackBy can preserve DOM and prevent reinitialization; cache expensive template transforms (memoize pipes) and add a pre-push lint hook to enforce subscription and typing rules.
AI-written summary · about
chapters (9)
- 0:00Start
- 16:26Prevent the Subscription
- 18:00Usage of a Sink Pipe
- 21:19Linter Rules
- 21:53Statical Code Analysis
- 22:32What Is the First Programming Concept You Learn When You Learn Programming
- 23:02Virtual Scrolling
- 30:09Types of Pipes
- 34:33State Management
related talks
34mBad Practices, how you should NOT do in Angular world
09mCommon Angular Gotchas
41mThe most infamous code smells in Angular Applications
22mThe dark side of tuning Angular performance
31mOptimized Angular apps: smaller, faster, better
45mOptimized Angular apps: smaller, faster, better
44mRockin’ in the Angular World
40mOptimized Angular Apps: Smaller, Faster, Better