Answer
Tree-shaking removes unused code from the bundle.
It results in smaller builds, faster load times, and better performance.
Quick Answer
Tree-shaking is a build optimization that removes unused code from the final bundle. Angular's build system (via Webpack/Rollup) analyzes imports and removes code that's never actually used. Angular's standalone components, providedIn: "root" services, and pure functions all support tree-shaking. This is why unused Angular features don't bloat the bundle.
S
SugharaIQ Editorial Team
Verified Answer
This answer has been peer-reviewed by industry experts holding senior engineering roles to ensure technical accuracy and relevance for modern interview standards.
Want to bookmark, take notes, or join discussions?
Sign in to access all features and personalize your learning experience.
Source: SugharaIQ