How Node.js differs from browser JavaScript in Node.js - Visual Walkthrough

Concept Flow - How Node.js differs from browser JavaScript

Write JS code

↓

Run in Browser

→Browser JS Engine

↓

DOM & BOM APIs

↓

Limited FS, Network

↓

Run in Node.js

→Node.js JS Engine

↓

Full FS, Network, OS APIs

JavaScript code runs in two places: browser and Node.js. Browser JS has access to web page features, Node.js has access to system features.

Execution Sample

Node.js

console.log(typeof window);
console.log(typeof process);
console.log(typeof document);

This code checks which global objects exist in Node.js vs browser.

Execution Table

Step	Expression	Evaluation in Browser	Evaluation in Node.js	Explanation
1	typeof window	"object"	"undefined"	Browser has 'window' object; Node.js does not
2	typeof process	"undefined"	"object"	'process' exists in Node.js, not in browser
3	typeof document	"object"	"undefined"	Browser has 'document' for DOM; Node.js does not
4	console.log('Hello')	Prints 'Hello' in browser console	Prints 'Hello' in terminal	Console works in both but output location differs
5	require('fs')	Error: require not defined	Returns FS module object	Node.js supports require for modules; browser does not
6	fetch('url')	Available as browser API	Available in Node.js 18+ as global	Fetch API now available in both but was browser-only
7	process.platform	"undefined"	"string"	Node.js can access OS info; browser cannot
8	Exit	-	-	Execution ends after checking key differences

💡 All key global objects checked; differences between environments shown

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
window	undefined	object (browser)	undefined (node)	undefined (node)	undefined (node)
process	undefined	undefined (browser)	object (node)	object (node)	object (node)
document	undefined	object (browser)	undefined (node)	undefined (node)	undefined (node)

Key Moments - 3 Insights

Why does 'window' exist in browser but not in Node.js?

'window' represents the browser's global object including the webpage. Node.js runs outside browser, so it has no 'window' (see execution_table step 1).

Why can Node.js use 'require' but browser cannot?

'require' is Node.js's way to load modules from files or packages. Browsers use different module systems and do not have 'require' (see execution_table step 5).

Is 'fetch' available in both environments?

Originally only browsers had 'fetch'. Node.js added it globally in version 18+. So now both can use it, but older Node.js versions do not have it (see execution_table step 6).

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'typeof process' in Node.js at step 2?

A "object"

B "undefined"

C "function"

D "string"

💡 Hint

Check the 'Evaluation in Node.js' column at step 2 in the execution_table.

At which step does 'require' cause an error in the browser?

A Step 3

B Step 6

C Step 5

D Step 7

💡 Hint

Look for 'require' usage and browser evaluation in the execution_table.

If you run this code in Node.js: console.log(typeof window), what will it print?

A "object"

B "undefined"

C "function"

D "null"

💡 Hint

Refer to step 1 in the execution_table under 'Evaluation in Node.js'.

Concept Snapshot

Node.js and browser JavaScript share the language but differ in environment.
Browser JS has 'window', 'document', DOM APIs.
Node.js has 'process', 'require', file system, OS APIs.
Some APIs like 'fetch' now exist in both.
Code behavior depends on available global objects and modules.

Full Transcript

This visual execution shows how JavaScript behaves differently in Node.js versus browsers. We check key global objects like 'window', 'process', and 'document'. In browsers, 'window' and 'document' exist for web page control, but Node.js lacks these because it runs outside the browser. Node.js provides 'process' and 'require' for system access and module loading, which browsers do not have. The 'fetch' API is available in browsers and now also in recent Node.js versions. This helps beginners see clearly what objects and features are available depending on where JavaScript runs.

Practice

1. Which of the following is a key difference between Node.js and browser JavaScript?

easy

A. Browser JavaScript can run server-side code, but Node.js cannot.

B. Browser JavaScript can access databases directly, but Node.js cannot.

C. Node.js runs only inside web pages, while browser JavaScript runs on servers.

D. Node.js can access the file system, but browser JavaScript cannot.

Solution

1. Step 1: Understand environment capabilities

   Node.js runs outside the browser and can access system resources like files.

2. Step 2: Compare browser limitations

   Browser JavaScript runs inside web pages and cannot access the file system for security reasons.

3. Final Answer:

   Node.js can access the file system, but browser JavaScript cannot. -> Option D

4. Quick Check:

   File system access = Node.js only [OK]

Hint: Remember: Node.js can read files; browsers cannot [OK]

Common Mistakes:

• Thinking browser JavaScript can access local files directly
• Confusing server-side and client-side roles
• Assuming Node.js runs inside web pages

2. Which syntax correctly imports the built-in 'fs' module in Node.js?

easy

A. import fs from 'fs';

B. const fs = require('fs');

C. let fs = import('fs');

D. var fs = fetch('fs');

Solution

1. Step 1: Identify Node.js import syntax

   Node.js traditionally uses CommonJS syntax: const fs = require('fs');.

2. Step 2: Check other options

   import fs from 'fs'; is ES module syntax, which requires special setup; var fs = fetch('fs'); and let fs = import('fs'); are invalid for module import.

3. Final Answer:

   const fs = require('fs'); -> Option B

4. Quick Check:

   CommonJS require() syntax = const fs = require('fs'); [OK]

Hint: Use require() to import built-in modules in Node.js [OK]

Common Mistakes:

• Using browser import syntax without Node.js ES module setup
• Confusing fetch() with module import
• Trying to use import() as a variable assignment

3. What will the following Node.js code output?

console.log(typeof window);

medium

A. "undefined"

B. "object"

C. "function"

D. "null"

Solution

1. Step 1: Understand the 'window' object context

   The 'window' object exists in browsers as the global object for the page.

2. Step 2: Check Node.js global objects

   Node.js does not have a 'window' object, so it is undefined.

3. Final Answer:

   "undefined" -> Option A

4. Quick Check:

   window in Node.js = undefined [OK]

Hint: window is browser-only; Node.js has no window [OK]

Common Mistakes:

• Assuming window exists in Node.js
• Confusing global and window objects
• Expecting 'object' type for window in Node.js

4. Identify the error in this Node.js code snippet:

import fs from 'fs';
const data = fs.readFileSync('file.txt', 'utf8');
console.log(data);

medium

A. The file path must be absolute, not relative.

B. readFileSync requires a callback function.

C. Using import without enabling ES modules causes a syntax error.

D. console.log cannot print file contents.

Solution

1. Step 1: Check import syntax in Node.js

   By default, Node.js uses CommonJS; import requires ES module setup or .mjs extension.

2. Step 2: Validate readFileSync usage

   readFileSync is synchronous and does not need a callback.

3. Final Answer:

   Using import without enabling ES modules causes a syntax error. -> Option C

4. Quick Check:

   import needs ES module setup in Node.js [OK]

Hint: Use require() or enable ES modules for import [OK]

Common Mistakes:

• Thinking readFileSync needs a callback
• Assuming relative paths always cause errors
• Believing console.log can't print strings

5. You want to write a Node.js script that reads a file and sends its content to a web page. Which approach correctly uses Node.js features to do this?

hard

A. Use Node.js to read the file with 'fs', then serve it via an HTTP server module.

B. Use browser JavaScript to read the file directly and send it to the server.

C. Use Node.js to run code inside the browser to access the file system.

D. Use browser JavaScript to create an HTTP server and read files.

Solution

1. Step 1: Understand Node.js capabilities

   Node.js can read files using 'fs' and create servers using 'http' or similar modules.

2. Step 2: Identify correct client-server roles

   Browser JavaScript cannot read files directly from disk or create servers; Node.js handles server tasks.

3. Final Answer:

   Use Node.js to read the file with 'fs', then serve it via an HTTP server module. -> Option A

4. Quick Check:

   Node.js reads files and serves content [OK]

Hint: Node.js handles files and servers; browsers handle UI [OK]

Common Mistakes:

• Expecting browser JS to read local files without user action
• Trying to run server code inside the browser
• Confusing client and server responsibilities