Why modules are needed in TypeScript - Quick Recap

Recall & Review

beginner

What is a module in TypeScript?

A module is a file that contains code (like variables, functions, or classes) which can be shared and used in other files.

beginner

Why do we need modules in TypeScript?

Modules help organize code by splitting it into smaller, manageable parts and avoid name conflicts by keeping code private unless exported.

intermediate

How do modules help avoid name conflicts?

Each module has its own scope, so variables or functions inside one module don’t clash with those in another unless explicitly shared.

beginner

What keywords are used to share code between modules?

The export keyword is used to share code, and import is used to bring that code into another module.

intermediate

How do modules improve code maintainability?

By breaking code into modules, it becomes easier to update, test, and reuse parts without affecting the whole program.

What is the main purpose of modules in TypeScript?

A To make code run faster

B To remove all variables

C To write code without any functions

D To organize code and avoid name conflicts

Modules help organize code and prevent name conflicts by keeping code scoped.

Which keyword is used to share code from a module?

A module

B import

C export

D include

The export keyword shares code from a module.

How do modules help with code scope?

A They make all variables global

B They keep variables and functions private unless exported

C They delete unused variables

D They convert code to plain text

Modules keep code private unless explicitly exported, avoiding conflicts.

What keyword do you use to bring code from another module?

A import

B export

C require

D include

The import keyword brings code from another module.

Which benefit is NOT provided by using modules?

A Making code run without errors automatically

B Avoiding name conflicts

C Easier code maintenance

D Better code organization

Modules help organize and maintain code but do not automatically fix errors.

Explain why modules are important in TypeScript and how they help manage code.

Think about how splitting a big task into smaller tasks makes it easier to handle.

Describe how the export and import keywords work in TypeScript modules.

Imagine sharing toys with friends and asking to borrow theirs.

Practice

1. Why do we need modules in TypeScript?

easy

A. To split code into smaller, manageable parts

B. To make code run faster

C. To write code without any errors

D. To avoid using variables

Solution

1. Step 1: Understand the purpose of modules

   Modules help organize code by splitting it into smaller parts.

2. Step 2: Identify the main benefit

   This splitting makes code easier to manage and understand.

3. Final Answer:

   To split code into smaller, manageable parts -> Option A

4. Quick Check:

   Modules organize code = B [OK]

Hint: Modules help organize and manage code easily [OK]

Common Mistakes:

• Thinking modules make code faster
• Believing modules fix all errors automatically
• Confusing modules with variable declarations

2. Which of the following is the correct way to export a function named greet from a TypeScript module?

easy

A. function greet() { console.log('Hello'); }

B. export function greet() { console.log('Hello'); }

C. export greet function() { console.log('Hello'); }

D. function greet() { console.log('Hello'); } export greet;

Solution

1. Step 1: Recall correct export syntax

   In TypeScript, to export a function, use export function functionName() {}.

2. Step 2: Check each option

   export function greet() { console.log('Hello'); } uses correct syntax. Options B and C have wrong order or missing keywords. function greet() { console.log('Hello'); } does not export.

3. Final Answer:

   export function greet() { console.log('Hello'); } -> Option B

4. Quick Check:

   Correct export syntax = D [OK]

Hint: Use 'export' before function to export it [OK]

Common Mistakes:

• Placing 'export' after function name
• Forgetting to export the function
• Using invalid export syntax

3. Consider two TypeScript files:
// file1.ts
export const value = 42;
// file2.ts
import { value } from './file1';
console.log(value);
What will be the output when file2.ts is run?

medium

A. null

B. undefined

C. Error: Cannot find module './file1'

D. 42

Solution

1. Step 1: Understand export and import

   file1.ts exports a constant named value with 42. file2.ts imports it correctly.

2. Step 2: Predict console output

   Since import is correct, console.log(value) prints 42.

3. Final Answer:

   42 -> Option D

4. Quick Check:

   Imported value logs 42 = A [OK]

Hint: Imported constants print their exported values [OK]

Common Mistakes:

• Assuming import fails without file extension
• Expecting undefined without export
• Confusing import syntax

4. What is wrong with this TypeScript module code?

export const a = 10;
const b = 20;
import { b } from './moduleB';

medium

A. The import statement must be at the top before any other code

B. You cannot import a variable named 'b' if it's declared locally

C. You cannot import after export in the same file

D. There is no error in this code

Solution

1. Step 1: Check import statement placement

   In TypeScript, import statements must be at the top before any other code.

2. Step 2: Identify the error

   Here, import comes after export and variable declaration, which is invalid.

3. Final Answer:

   The import statement must be at the top before any other code -> Option A

4. Quick Check:

   Imports must be top-level = A [OK]

Hint: Always place imports at the top of the file [OK]

Common Mistakes:

• Placing imports after code
• Thinking imports can be anywhere
• Confusing import and export order

5. You have two modules:
// mathUtils.ts
export function add(x: number, y: number) { return x + y; }
export function multiply(x: number, y: number) { return x * y; }
// app.ts
import * as math from './mathUtils';
console.log(math.add(2, 3));
console.log(math.multiply(4, 5));
Why is using import * as math helpful in this case?

hard

A. It automatically fixes type errors in imported functions

B. It makes the code run faster by bundling functions

C. It groups all exports under one name to avoid name conflicts

D. It prevents the need to export functions in mathUtils.ts

Solution

1. Step 1: Understand import * as syntax

   This syntax imports all exported members under a single namespace object.

2. Step 2: Identify benefit

   Grouping exports under math avoids naming conflicts and keeps code organized.

3. Final Answer:

   It groups all exports under one name to avoid name conflicts -> Option C

4. Quick Check:

   Namespace import groups exports = C [OK]

Hint: Use 'import * as' to group exports under one name [OK]

Common Mistakes:

• Thinking it improves performance
• Believing it fixes type errors automatically
• Assuming exports are not needed