Tree shaking and dead code removal in Angular - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

How does Angular's tree shaking affect unused components?

Consider an Angular app where a component is declared but never used in any template or routing. What happens to this component during the build process with tree shaking enabled?

A The component is removed from the final bundle because it is not referenced anywhere.

B The component remains in the bundle but is marked as deprecated.

C The component causes a build error because it is declared but unused.

D The component is included in the bundle but its template is removed.

💡 Hint

Think about what tree shaking means for unused code.

Tree shaking removes code that is not referenced anywhere in the app. Since the component is never used, it is removed from the final bundle, reducing bundle size.

📝 Syntax

intermediate

Which import style helps Angular's tree shaking?

Given a utility library with many functions, which import style allows Angular's build tools to remove unused functions effectively?

A const utils = require('library');

B import * as utils from 'library';

C import 'library';

D import { usefulFunction } from 'library';

💡 Hint

Consider how named imports vs namespace imports affect static analysis.

Named imports allow the build tools to detect exactly which functions are used and remove the rest. Namespace imports or side-effect imports prevent effective tree shaking.

🔧 Debug

advanced

Why is dead code not removed in this Angular service?

Look at this Angular service code snippet:

export class DataService {
  fetchData() { return 'data'; }
  unusedMethod() { return 'unused'; }
}

Despite unusedMethod never being called, it remains in the final bundle. Why?

A Because the service is provided in root and the whole class is included.

B Because Angular cannot tree shake methods inside classes.

C Because the build configuration disables tree shaking.

D Because the method is public and thus always included.

💡 Hint

Think about how Angular includes services provided in root.

When a service is provided in root, Angular includes the entire class in the bundle. Tree shaking does not remove unused methods inside classes because the class is referenced as a whole.

🧠 Conceptual

advanced

What role does Angular's Ivy compiler play in dead code removal?

How does Angular's Ivy compiler improve tree shaking and dead code removal compared to the previous View Engine?

A Ivy disables tree shaking to improve runtime performance.

B Ivy bundles all components into a single file, preventing dead code removal.

C Ivy generates code that is more modular and easier for build tools to analyze and remove unused parts.

D Ivy requires manual configuration to enable dead code removal.

💡 Hint

Think about how code generation affects static analysis.

Ivy generates smaller, more modular code that allows build tools to detect and remove unused components and code more effectively than the older View Engine.

❓ state_output

expert

What is the final bundle size effect of importing a large unused Angular module?

In an Angular app, you import a large feature module but never use any of its components or services. What happens to the final bundle size after build with tree shaking?

A The module is completely removed from the bundle, no size increase.

B The entire module and its code remain in the bundle, increasing size significantly.

C The module code is included but minified to zero size.

D Only the module's metadata is included, but code is removed.

💡 Hint

Consider how Angular treats imported modules even if unused.

Importing a module causes Angular to include its code in the bundle. Tree shaking cannot remove the module because it is referenced by the import statement, even if its components are unused.

Practice

1. What is the main purpose of tree shaking in Angular?

easy

A. To remove unused code and imports during the build process

B. To add extra debugging information to the app

C. To increase the size of the final bundle

D. To automatically update Angular dependencies

Solution

1. Step 1: Understand tree shaking concept

   Tree shaking is a process that removes unused code and imports from the final build.

2. Step 2: Identify its effect in Angular

   In Angular, tree shaking helps reduce app size by excluding code that is never used.

3. Final Answer:

   To remove unused code and imports during the build process -> Option A

4. Quick Check:

   Tree shaking = remove unused code [OK]

Hint: Tree shaking removes unused code to shrink app size [OK]

Common Mistakes:

• Thinking tree shaking adds code instead of removing
• Confusing tree shaking with debugging tools
• Believing tree shaking updates dependencies automatically

2. Which syntax correctly imports a module that can be tree shaken in Angular?

easy

A. import * as Component from '@angular/core';

B. import Component from '@angular/core';

C. require('@angular/core').Component;

D. import { Component } from '@angular/core';

Solution

1. Step 1: Recognize ES module import syntax

   Angular uses ES module syntax: import { NamedExport } from 'module';

2. Step 2: Identify correct import for Component

   The correct syntax is importing Component as a named export inside curly braces.

3. Final Answer:

   import { Component } from '@angular/core'; -> Option D

4. Quick Check:

   Correct ES module import = import { Component } from '@angular/core'; [OK]

Hint: Use curly braces for named imports in Angular [OK]

Common Mistakes:

• Using default import syntax for named exports
• Using CommonJS require instead of ES import
• Importing everything as a namespace unnecessarily

3. Given this Angular service code, what will be removed by tree shaking if unusedMethod() is never called anywhere?

export class DataService {
  fetchData() { return 'data'; }
  unusedMethod() { return 'not used'; }
}

medium

A. Only fetchData will be kept; unusedMethod will be removed

B. Both fetchData and unusedMethod will be kept

C. Only unusedMethod will be kept; fetchData will be removed

D. Neither method will be removed

Solution

1. Step 1: Identify used and unused methods

   fetchData is assumed used; unusedMethod is never called anywhere.

2. Step 2: Apply tree shaking effect

   Tree shaking removes unused code like unusedMethod to reduce bundle size.

3. Final Answer:

   Only fetchData will be kept; unusedMethod will be removed -> Option A

4. Quick Check:

   Unused code removed = Only fetchData will be kept; unusedMethod will be removed [OK]

Hint: Unused methods get removed by tree shaking [OK]

Common Mistakes:

• Assuming all methods stay regardless of usage
• Confusing tree shaking with runtime errors
• Thinking tree shaking removes used code

4. You notice your Angular app bundle size is large despite removing unused components. What is a likely cause related to tree shaking?

medium

A. Your code uses only arrow functions

B. You are importing entire modules instead of specific components

C. You forgot to run the production build command

D. You are using lazy loading for modules

Solution

1. Step 1: Understand tree shaking limitations

   Tree shaking works best when importing specific parts, not whole modules.

2. Step 2: Identify import style impact

   Importing entire modules prevents tree shaking from removing unused parts, increasing bundle size.

3. Final Answer:

   You are importing entire modules instead of specific components -> Option B

4. Quick Check:

   Whole module imports block tree shaking = You are importing entire modules instead of specific components [OK]

Hint: Import specific parts, not whole modules, for tree shaking [OK]

Common Mistakes:

• Ignoring production build optimizations
• Thinking arrow functions affect tree shaking
• Believing lazy loading increases bundle size

5. How can you ensure a utility function in Angular is not removed by tree shaking even if it appears unused?

hard

A. Define it inside a component class without export

B. Mark it with a special comment like /* keep */

C. Export it and use it in a component or service

D. Use it only in test files

Solution

1. Step 1: Understand tree shaking criteria

   Tree shaking removes code not referenced anywhere in the app.

2. Step 2: Prevent removal by usage

   Exporting and using the function in components or services marks it as used, so it stays.

3. Final Answer:

   Export it and use it in a component or service -> Option C

4. Quick Check:

   Used code is kept by tree shaking = Export it and use it in a component or service [OK]

Hint: Use exported functions in app code to keep them [OK]

Common Mistakes:

• Thinking comments prevent tree shaking
• Defining functions without export to keep them
• Using functions only in tests to keep them