The most infamous code smells in Angular Applications
summary
A catalogue of concrete Angular failures and fixes: oversized shared modules bloat tests and hide responsibilities so the remedy is to break them up and core module only once to avoid state loss; nested subscriptions cause memory leaks so prefer switchMap and RxJS operators; shipping everything upfront kills load times so lazy load noncritical modules; constructors stuffed with many services signal a component doing too much; enforce TypeScript linters and prettier and adopt domain-based folders for maintainability.
AI-written summary · about
chapters (11)
- 0:00Start
- 2:50AngularJS
- 6:27Poor folder structure
- 8:44Poor TypeScript knowledge
- 10:46Poor Change Detection understanding
- 13:17Too many modules
- 18:31Redesign the module structure of the app
- 21:43Poor service design
- 24:56Lack of proper types
- 27:42Race conditions
- 31:14Scalability issues
related talks
44mRockin’ in the Angular World
19mTuning Your Angular Application
09mCommon Angular Gotchas
35mBad Practices, what NOT to do in Angular
28mUnleash The Power Of Angular With Knowledge of Patterns
34mBad Practices, how you should NOT do in Angular world
34mScalable Angular Architecture
22mCommon Challenges Facing Angular Enterprises