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.