Why modules are used in Javascript - Performance Analysis

Time Complexity: Why modules are used

O(n)

Understanding Time Complexity

We want to understand how using modules affects the time it takes for JavaScript code to run.

Specifically, we ask: does splitting code into modules change how fast it executes?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

// main.js
import { greet } from './greet.js';

function run() {
  for (let i = 0; i < 5; i++) {
    greet(i);
  }
}

run();

// greet.js
export function greet(num) {
  console.log(`Hello number ${num}`);
}
    

This code imports a function from another file and calls it multiple times in a loop.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The loop in run() calls greet() 5 times.
• How many times: Exactly 5 times, once per loop cycle.

How Execution Grows With Input

Imagine changing the loop count to different sizes.

Input Size (n)	Approx. Operations
10	10 calls to greet()
100	100 calls to greet()
1000	1000 calls to greet()

As the number of calls grows, the total work grows in the same way, directly with n.

Final Time Complexity

Time Complexity: O(n)

This means the time to run grows directly with how many times we call the function.

Common Mistake

[X] Wrong: "Using modules makes the code slower because it adds extra steps."

[OK] Correct: Modules organize code but do not add extra loops or repeated work during execution. The main time cost depends on how many times functions run, not on splitting code into files.

Interview Connect

Understanding how modules affect code helps you explain clean code design without worrying about slowing down programs. This skill shows you think about both structure and performance.

Self-Check

"What if the greet function itself contained a loop that runs n times? How would that change the time complexity?"

Practice

1. Why do JavaScript modules help in programming?

easy

A. They split code into smaller, manageable parts.

B. They make the code run faster.

C. They remove the need for variables.

D. They automatically fix bugs.

Solution

1. Step 1: Understand the purpose of modules

   Modules are designed to divide code into smaller pieces that are easier to manage.

2. Step 2: Compare options with module benefits

   Only splitting code into smaller parts matches the main use of modules.

3. Final Answer:

   They split code into smaller, manageable parts. -> Option A

4. Quick Check:

   Modules = smaller code parts [OK]

Hint: Modules break code into parts for easy management [OK]

Common Mistakes:

• Thinking modules speed up code automatically
• Believing modules remove variables
• Assuming modules fix bugs by themselves

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

easy

A. export greet() {}

B. export function greet() {}

C. function export greet() {}

D. export = greet()

Solution

1. Step 1: Recall JavaScript export syntax

   The correct syntax to export a function is to write export function functionName() {}.

2. Step 2: Check each option

   Only export function greet() {} matches the correct syntax for exporting a function.

3. Final Answer:

   export function greet() {} -> Option B

4. Quick Check:

   Export function syntax = export function name() [OK]

Hint: Use 'export function name()' to export functions [OK]

Common Mistakes:

• Placing export after function keyword
• Using incorrect export assignment syntax
• Omitting the function keyword

3. What will be the output of the following code?

// file: math.js
export function add(a, b) { return a + b; }

// file: main.js
import { add } from './math.js';
console.log(add(3, 4));

medium

A. 34

B. undefined

C. Error: add is not defined

D. 7

Solution

1. Step 1: Understand import and export usage

   The function add is exported from math.js and imported correctly in main.js.

2. Step 2: Calculate the function output

   Calling add(3, 4) returns 3 + 4 = 7, which is logged.

3. Final Answer:

   7 -> Option D

4. Quick Check:

   3 + 4 = 7 [OK]

Hint: Imported functions run normally if exported correctly [OK]

Common Mistakes:

• Forgetting to export the function
• Using wrong import syntax
• Expecting string concatenation instead of addition

4. Identify the error in this module usage:

// file: utils.js
export function greet() { console.log('Hello'); }

// file: app.js
import greet from './utils.js';
greet();

medium

A. Missing curly braces in import statement

B. Function greet is not exported

C. Wrong file path in import

D. greet is called without parentheses

Solution

1. Step 1: Check export and import syntax

   The function greet is exported as a named export, so import must use curly braces.

2. Step 2: Identify import statement error

   Importing without curly braces tries to import a default export, which does not exist here.

3. Final Answer:

   Missing curly braces in import statement -> Option A

4. Quick Check:

   Named exports need braces in import [OK]

Hint: Use braces for named imports, no braces for default [OK]

Common Mistakes:

• Confusing named and default exports
• Calling function without parentheses
• Incorrect file path usage

5. You want to organize a large JavaScript project by splitting code into modules. Which of these is NOT a benefit of using modules?

hard

A. They help avoid naming conflicts by keeping variables local.

B. They allow code reuse across different files.

C. They automatically optimize code performance.

D. They make code easier to maintain and understand.

Solution

1. Step 1: Review benefits of modules

   Modules help organize code, avoid conflicts, and allow reuse and maintenance.

2. Step 2: Identify the incorrect statement

   Modules do not automatically optimize performance; optimization is separate.

3. Final Answer:

   They automatically optimize code performance. -> Option C

4. Quick Check:

   Modules organize, not optimize code [OK]

Hint: Modules organize and reuse code, not speed it up automatically [OK]

Common Mistakes:

• Assuming modules improve speed automatically
• Confusing code organization with performance
• Ignoring variable scope benefits