Importing dependencies directly in Angular - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does it mean to import dependencies directly in Angular?

It means bringing in specific functions, classes, or modules from external libraries or Angular packages right where you need them in your code, so you can use them easily.

beginner

How do you import a component from Angular's core package?

You write: <code>import { Component } from '@angular/core';</code> This brings the Component decorator into your file.

beginner

Why is it better to import only what you need instead of the whole library?

Importing only what you need keeps your app smaller and faster because it avoids loading extra code that you don't use.

beginner

Show an example of importing a service directly in Angular.

Example: <code>import { HttpClient } from '@angular/common/http';</code> This lets you use HttpClient to make web requests.

beginner

What happens if you forget to import a dependency you use in your Angular file?

Your code will give an error because Angular won't know what that function or class means without the import.

How do you import the RouterModule from Angular's router package?

A import RouterModule from 'angular/router';

B import { RouterModule } from 'angular-core';

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

D import RouterModule from '@angular/core/router';

The correct syntax is import { RouterModule } from '@angular/router'; which imports RouterModule from the router package.

What is the benefit of importing dependencies directly in Angular?

A It helps keep the app size smaller and faster.

B It removes the need for modules.

C It automatically fixes bugs.

D It makes the app load slower.

Importing only what you need keeps the app smaller and faster by avoiding extra unused code.

Which of these is a correct import statement in Angular?

A import { Injectable } from '@angular/core';

B import Injectable from '@angular/core';

C import { Injectable } from 'angular/core';

D import Injectable from 'angular';

Correct syntax uses curly braces and the exact package name: import { Injectable } from '@angular/core';

What error might you see if you forget to import a dependency?

A SyntaxError: Unexpected token

B ReferenceError: X is not defined

C TypeError: Cannot read property

D No error, code runs fine

If a dependency is missing, you often get a ReferenceError saying the item is not defined.

Where should you place import statements in an Angular file?

A Anywhere in the file

B At the bottom of the file

C Inside functions

D At the top of the file

Imports should be at the top of the file before any other code.

Explain how to import a dependency directly in Angular and why it is important.

Think about how you bring tools into your workspace only when you need them.

Describe what happens if you use a class or function in Angular without importing it first.

Imagine trying to use a tool you never took out of the toolbox.

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 '*'