Running JavaScript using Node.js - Time & Space Complexity

Time Complexity: Running JavaScript using Node.js

O(n)

Understanding Time Complexity

When running JavaScript with Node.js, it's helpful to understand how the time your code takes grows as you give it more work.

We want to see how the number of operations changes when the input size changes.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

const fs = require('fs');

function readFiles(fileNames) {
  fileNames.forEach(name => {
    const content = fs.readFileSync(name, 'utf8');
    console.log(content.length);
  });
}

readFiles(['file1.txt', 'file2.txt', 'file3.txt']);
    

This code reads several files one by one and prints their length.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Reading each file synchronously inside a loop.
• How many times: Once for each file in the input list.

How Execution Grows With Input

As you add more files, the total time grows roughly in direct proportion to the number of files.

Input Size (n)	Approx. Operations
10	10 file reads
100	100 file reads
1000	1000 file reads

Pattern observation: Doubling the number of files roughly doubles the work done.

Final Time Complexity

Time Complexity: O(n)

This means the time grows in a straight line with the number of files you read.

Common Mistake

[X] Wrong: "Reading multiple files at once will always be faster and have constant time."

[OK] Correct: Even if you read files in parallel, the total work still depends on how many files there are, so time grows with input size.

Interview Connect

Understanding how your Node.js code scales with input size shows you can write efficient programs and reason about performance clearly.

Self-Check

"What if we changed from reading files synchronously to reading them asynchronously with promises? How would the time complexity change?"

Practice

1. What does the command node filename.js do?

easy

A. Runs the JavaScript code inside filename.js using Node.js

B. Opens the file filename.js in a text editor

C. Compiles filename.js into a different programming language

D. Deletes the file filename.js from your computer

Solution

1. Step 1: Understand the command node filename.js

   This command tells Node.js to run the JavaScript code inside the file named filename.js.

2. Step 2: Identify what Node.js does

   Node.js executes JavaScript code outside the browser, so it runs the code in the file.

3. Final Answer:

   Runs the JavaScript code inside filename.js using Node.js -> Option A

4. Quick Check:

   node filename.js runs code = C [OK]

Hint: Node runs JavaScript files given after the command [OK]

Common Mistakes:

• Thinking it opens the file in an editor
• Confusing running with compiling
• Assuming it deletes the file

2. Which of the following is the correct way to start an interactive Node.js session in the terminal?

easy

A. run node

B. node filename.js

C. node

D. start node.js

Solution

1. Step 1: Recall how to start Node.js interactively

   Typing node alone in the terminal starts an interactive JavaScript session.

2. Step 2: Check other options

   node filename.js runs a file, not interactive mode; run node and start node.js are invalid commands.

3. Final Answer:

   node -> Option C

4. Quick Check:

   Just node starts interactive mode [OK]

Hint: Just type 'node' to enter interactive mode [OK]

Common Mistakes:

• Adding extra words like 'run' or 'start'
• Confusing running a file with interactive mode
• Using file names when none are needed

3. What will be the output when running this file with node test.js?

console.log('Hello from Node.js!');

medium

A. SyntaxError

B. Hello from Node.js!

C. undefined

D. No output

Solution

1. Step 1: Understand the code inside test.js

   The code uses console.log to print a string to the console.

2. Step 2: Know what Node.js does when running the file

   Node.js executes the code and prints the string to the terminal.

3. Final Answer:

   Hello from Node.js! -> Option B

4. Quick Check:

   console.log prints text = Hello from Node.js! [OK]

Hint: console.log prints output to terminal [OK]

Common Mistakes:

• Expecting no output
• Confusing console.log with return value
• Thinking it causes an error

4. You try to run node app.js but get an error: SyntaxError: Unexpected token. What is the most likely cause?

medium

A. You typed node incorrectly

B. You forgot to save app.js before running

C. Node.js is not installed on your computer

D. The app.js file has invalid JavaScript syntax

Solution

1. Step 1: Understand the error message

   A SyntaxError: Unexpected token means the JavaScript code has a syntax mistake.

2. Step 2: Check other options

   Typing node wrong usually gives a different error; missing Node.js causes 'command not found'; unsaved file won't run but usually no syntax error.

3. Final Answer:

   The app.js file has invalid JavaScript syntax -> Option D

4. Quick Check:

   SyntaxError means code syntax is wrong [OK]

Hint: SyntaxError means code inside file is wrong [OK]

Common Mistakes:

• Assuming Node.js is missing
• Thinking the command was typed wrong
• Not saving file before running

5. You want to quickly test a small JavaScript expression without creating a file. What is the best way to do this using Node.js?

hard

A. Run node in terminal to open interactive mode and type the expression

B. Create a file, write the code, then run node filename.js

C. Use npm start to run the expression

D. Open a browser and run the code in the console

Solution

1. Step 1: Identify how to run code without a file

   Running node alone opens an interactive session where you can type JavaScript directly.

2. Step 2: Compare other options

   Creating a file is slower; npm start runs scripts defined in package.json, not quick tests; browser console is outside Node.js environment.

3. Final Answer:

   Run node in terminal to open interactive mode and type the expression -> Option A

4. Quick Check:

   Interactive mode = quick testing [OK]

Hint: Use just 'node' to test code quickly without files [OK]

Common Mistakes:

• Thinking npm start runs any code
• Believing browser console is Node.js
• Always creating files for small tests