Tree shaking and dead code removal in Angular

Introduction

Tree shaking helps remove unused code from your Angular app. This makes your app smaller and faster to load.

When you want to reduce the size of your Angular app for faster loading.

When you have many components or services but only use some of them.

When you want to improve app performance by sending less code to the browser.

When you want to keep your app clean by removing unused functions or variables.

Syntax

Angular

No special code is needed. Angular CLI and build tools handle tree shaking automatically during production builds.

Tree shaking works best with ES modules (import/export syntax).

Dead code removal happens during the Angular production build using tools like Webpack and Terser.

Examples

If ComponentB is never used, tree shaking will remove it from the final bundle.

Angular

import { ComponentA } from './component-a';
import { ComponentB } from './component-b';

@Component({ /* ... */ })
export class AppComponent {
  // Only ComponentA is used here
  useComponentA() {
    new ComponentA();
  }
}

The unusedHelper function will be removed during dead code elimination.

Angular

// Unused function
function unusedHelper() {
  console.log('This is never called');
}

// Used function
function usedHelper() {
  console.log('This is called');
}

usedHelper();

Sample Program

In this example, unusedMethod is never called. Angular's build tools will remove it from the final app bundle during production build.

Angular

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

@Component({
  selector: 'app-root',
  template: `<h1>Hello Angular</h1>`
})
export class AppComponent {
  usedMethod() {
    console.log('Used method called');
  }

  unusedMethod() {
    console.log('Unused method');
  }

  constructor() {
    this.usedMethod();
  }
}

Important Notes

Always build your Angular app with ng build --prod to enable tree shaking and dead code removal.

Keep your imports clean and avoid importing unused modules to help tree shaking work better.

Summary

Tree shaking removes unused imports and code automatically during production builds.

Dead code removal deletes functions or variables that are never used.

This makes your Angular app smaller and faster to load.

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