Tree shaking and dead code removal in Angular - Step-by-Step Execution

Concept Flow - Tree shaking and dead code removal

Start: Angular build

↓

Analyze imports and exports

↓

Mark used code

↓

Identify unused code

↓

Remove unused code (dead code)

↓

Generate optimized bundle

↓

Output smaller, efficient app

Angular build analyzes code usage, marks used parts, removes unused code, and outputs a smaller app bundle.

Execution Sample

Angular

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

@Component({ selector: 'app-root', template: '<h1>Hello</h1>' })
export class AppComponent {
  title = 'My App';
}

This Angular component imports a function that is never used, which tree shaking will remove.

Execution Table

Step	Action	Code Analyzed	Used Code Marked	Dead Code Removed	Bundle Size Impact
1	Start build	All project files	None yet	None yet	Full size
2	Analyze imports	AppComponent, utils	AppComponent class	unusedFunction identified unused	No change yet
3	Mark used code	AppComponent class and dependencies	AppComponent class marked used	unusedFunction marked unused	No change yet
4	Remove dead code	unusedFunction	N/A	unusedFunction removed	Bundle smaller
5	Generate bundle	Used code only	AppComponent class	unusedFunction gone	Optimized smaller bundle
6	Output	Final app bundle	Only used code included	Dead code removed	Smaller, faster app

💡 Build completes with unused code removed, resulting in smaller bundle size.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
usedCode	[]	[AppComponent]	[AppComponent]	[AppComponent]	[AppComponent]
deadCode	[]	[unusedFunction]	[unusedFunction]	[]	[]
bundleSize	Full	Full	Full	Smaller	Smaller

Key Moments - 2 Insights

Why is the unusedFunction removed even though it is imported?

Because the build process marks it as unused (see execution_table step 3) and removes it to reduce bundle size (step 4).

Does tree shaking remove code that is dynamically used?

No, only code that static analysis shows as unused is removed. Dynamic usage may prevent removal.

Visual Quiz - 3 Questions

Look at the execution_table at step 3, which code is marked as used?

A AppComponent class

B unusedFunction

C Both AppComponent and unusedFunction

D None

💡 Hint

Check the 'Used Code Marked' column at step 3 in execution_table.

At which step is the dead code actually removed?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Look at the 'Dead Code Removed' column in execution_table.

If the unusedFunction was used dynamically, how would the bundleSize change after step 4?

A It would become smaller

B It would stay full size

C It would be empty

D It would be larger

💡 Hint

Refer to variable_tracker 'bundleSize' and the explanation in key_moments about dynamic usage.

Concept Snapshot

Tree shaking in Angular removes unused code during build.
It analyzes imports and usage to mark code as used or unused.
Unused code is removed to reduce bundle size.
This makes the app faster and smaller.
Dynamic code usage may prevent removal.

Full Transcript

Tree shaking and dead code removal in Angular happen during the build process. The build starts by analyzing all project files and imports. It marks which code is actually used, like the AppComponent class, and identifies unused code, such as an imported but unused function. Then, it removes this dead code to make the final app bundle smaller and more efficient. This process helps the app load faster and use less memory. However, code used dynamically might not be removed because the build cannot detect its usage statically.

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