Why modules are needed in TypeScript - See It in Action

Why modules are needed in TypeScript

📖 Scenario: Imagine you are building a small library of math functions. You want to keep your code organized and avoid mixing everything in one file. Modules help you split your code into parts that can be used separately and safely.

🎯 Goal: You will create two TypeScript files: one module that exports a function, and another file that imports and uses that function. This shows why modules are needed to organize and reuse code.

📋 What You'll Learn

Create a module file that exports a function

Create a main file that imports the function from the module

Use the imported function to calculate and display a result

💡 Why This Matters

🌍 Real World

In real projects, modules help keep code organized and manageable as projects grow.

💼 Career

Understanding modules is essential for working on professional TypeScript or JavaScript projects where code reuse and organization matter.

1

Create a module file with a function

Create a file named mathUtils.ts and write a function called add that takes two numbers a and b and returns their sum. Export this function using export.

Typescript

// Your code here

Hint

Use export function add(a: number, b: number): number { return a + b; } to create and export the function.

2

Create a main file to import the function

Create a file named main.ts. Import the add function from ./mathUtils using import { add } from './mathUtils';.

Typescript

// Your code here

Hint

Use import { add } from './mathUtils'; to bring the function into main.ts.

3

Use the imported function to calculate a sum

In main.ts, call the add function with arguments 5 and 7 and store the result in a variable called result.

Typescript

import { add } from './mathUtils';

// Your code here

Hint

Write const result = add(5, 7); to call the function and save the sum.

4

Print the result to the console

In main.ts, write a console.log statement to display the value of result.

Typescript

import { add } from './mathUtils';

const result = add(5, 7);

// Your code here

Hint

Use console.log(result); to show the sum in the console.

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