Importing dependencies directly in Angular - Performance & Optimization

Performance: Importing dependencies directly

MEDIUM IMPACT

This affects the bundle size and initial load time by controlling how much code is included and when it is loaded.

Including Angular Material components in a module

Angular

import { MatButtonModule } from '@angular/material/button';
import { MatIconModule } from '@angular/material/icon';
import { MatCardModule } from '@angular/material/card';
import { MatInputModule } from '@angular/material/input';
import { MatToolbarModule } from '@angular/material/toolbar';

@NgModule({
  imports: [MatButtonModule, MatIconModule, MatCardModule, MatInputModule, MatToolbarModule],
})
export class AppModule {}

Importing each component directly includes only needed code, reducing bundle size.

📈 Performance GainSaves 150kb+ in bundle size, improving LCP by 200ms

Including Angular Material components in a module

Angular

import { MatButtonModule, MatIconModule, MatCardModule, MatInputModule, MatToolbarModule } from '@angular/material';

@NgModule({
  imports: [MatButtonModule, MatIconModule, MatCardModule, MatInputModule, MatToolbarModule],
})
export class AppModule {}

Importing from the root '@angular/material' imports the entire library, increasing bundle size unnecessarily.

📉 Performance CostAdds 200kb+ to bundle, increasing LCP by 300ms on average

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Import from root package	N/A	N/A	High due to large JS bundle	[X] Bad
Import dependencies directly	N/A	N/A	Lower due to smaller JS bundle	[OK] Good

Rendering Pipeline

Direct imports reduce the JavaScript bundle size, which speeds up parsing and execution during the loading phase, leading to faster style calculation and layout.

→Parsing & Compilation

→Style Calculation

→Layout

⚠️ BottleneckParsing & Compilation of large bundles

Core Web Vital Affected

LCP

This affects the bundle size and initial load time by controlling how much code is included and when it is loaded.

Optimization Tips

1Always import Angular dependencies from their specific entry points, not the root package.

2Smaller bundles lead to faster parsing and quicker page load times.

3Reducing bundle size improves Largest Contentful Paint (LCP) and user experience.

Performance Quiz - 3 Questions

What is the main performance benefit of importing Angular dependencies directly?

A Easier to write code

B More features available automatically

C Smaller bundle size and faster page load

D Improves CSS rendering speed

DevTools: Network

How to check: Open DevTools > Network tab > Reload page > Filter by JS files > Check size of Angular Material related files

What to look for: Look for large bundle sizes indicating root imports; smaller, modular files indicate direct imports

Practice

1. What is the main purpose of importing dependencies directly in Angular?

easy

A. To create new Angular components automatically

B. To run Angular applications without a server

C. To use code from other files or libraries in your current file

D. To style components with CSS

Solution

1. Step 1: Understand what importing means

   Importing means bringing code from other files or libraries into your current file so you can use it.

2. Step 2: Identify the purpose in Angular

   In Angular, importing dependencies directly allows you to use components, services, or modules defined elsewhere.

3. Final Answer:

   To use code from other files or libraries in your current file -> Option C

4. Quick Check:

   Importing = Using external code [OK]

Hint: Importing means bringing code in from other files [OK]

Common Mistakes:

• Thinking importing creates components automatically
• Confusing importing with styling
• Assuming importing runs the app

2. Which of the following is the correct syntax to import the HttpClient from Angular's common HTTP package?

easy

A. import { HttpClient } from '@angular/common/http';

B. import HttpClient from '@angular/common/http';

C. import (HttpClient) from '@angular/common/http';

D. import * HttpClient from '@angular/common/http';

Solution

1. Step 1: Recall Angular import syntax

   Angular uses curly braces to import specific parts from a package or file.

2. Step 2: Match syntax with options

   import { HttpClient } from '@angular/common/http'; uses curly braces correctly: import { HttpClient } from '@angular/common/http';

3. Final Answer:

   import { HttpClient } from '@angular/common/http'; -> Option A

4. Quick Check:

   Curly braces for specific imports [OK]

Hint: Use curly braces to import specific parts [OK]

Common Mistakes:

• Omitting curly braces for named imports
• Using parentheses instead of braces
• Using incorrect import keywords

3. Given the following import statement in an Angular component:

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

What will happen if you remove the curly braces around Component?

medium

A. The import will work normally without errors

B. You will get a syntax error because named imports need curly braces

C. Angular will import the entire module instead

D. The component will import but not function correctly

Solution

1. Step 1: Understand named imports syntax

   Named imports require curly braces to specify exactly what to import from a module.

2. Step 2: Analyze removing curly braces effect

   Removing curly braces tries to import a default export, which @angular/core does not provide for Component, causing a syntax error.

3. Final Answer:

   You will get a syntax error because named imports need curly braces -> Option B

4. Quick Check:

   Named imports require braces [OK]

Hint: Named imports always need curly braces [OK]

Common Mistakes:

• Assuming import works without braces
• Confusing default and named imports
• Thinking Angular auto-corrects import syntax

4. You wrote this import in your Angular component:

import { RouterModule } from '@angular/router';

But you get an error saying Cannot find module '@angular/router'. What is the most likely cause?

medium

A. RouterModule is not exported from @angular/router

B. You used curly braces incorrectly

C. You need to import RouterModule from @angular/core instead

D. You forgot to install the @angular/router package

Solution

1. Step 1: Understand the error message

   The error means the module '@angular/router' is not found in your project dependencies.

2. Step 2: Identify common cause

   This usually happens if the package is not installed via npm or yarn.

3. Final Answer:

   You forgot to install the @angular/router package -> Option D

4. Quick Check:

   Missing package causes module not found error [OK]

Hint: Check if package is installed when module not found [OK]

Common Mistakes:

• Assuming import syntax is wrong
• Importing from wrong package
• Ignoring installation step

5. You want to import two Angular features, NgIf and NgFor, from @angular/common in a single import statement. Which is the correct way to do this?

hard

A. import { NgIf, NgFor } from '@angular/common';

B. import NgIf, NgFor from '@angular/common';

C. import { NgIf } and { NgFor } from '@angular/common';

D. import * as NgIf, NgFor from '@angular/common';

Solution

1. Step 1: Recall syntax for multiple named imports

   Use one import statement with curly braces listing all names separated by commas.

2. Step 2: Check options for correct syntax

   import { NgIf, NgFor } from '@angular/common'; correctly imports both NgIf and NgFor in one statement with braces and commas.

3. Final Answer:

   import { NgIf, NgFor } from '@angular/common'; -> Option A

4. Quick Check:

   Multiple named imports use commas inside braces [OK]

Hint: List multiple imports inside one pair of braces separated by commas [OK]

Common Mistakes:

• Using multiple import statements unnecessarily
• Omitting commas between imports
• Using incorrect keywords like 'and' or '*'