Angular - Performance Optimization
If your Angular app's bundle remains large despite removing unused components, which issue might be blocking tree shaking?
If your Angular app's bundle remains large despite removing unused components, which issue might be blocking tree shaking?
medium📝 Debug Q6 of 15
Step-by-Step Solution
Solution:
Step 1: Identify common tree shaking blockers
Importing entire libraries prevents removal of unused code.Step 2: Understand other options
Angular CLI, AOT, and lazy loading help reduce bundle size, not block tree shaking.Final Answer:
Importing entire libraries instead of specific modules -> Option CQuick Check:
Whole-library imports block tree shaking [OK]
Quick Trick: Avoid full library imports to enable tree shaking [OK]
Common Mistakes:
- Blaming Angular CLI or AOT for bundle size
- Ignoring import styles
- Assuming lazy loading increases bundle size
Master "Performance Optimization" in Angular
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Angular Quizzes