Node.js vs Browser JavaScript

Node.js vs Browser JavaScript

JavaScript runs in two different environments:

1. Browser (Client-side)

2. Node.js (Server-side)

Although both use JavaScript, the environment, features, and purpose are different.

1. Purpose

2. Global Object

Example:

3. APIs Available

Browser provides:

• document (DOM)

• window

• localStorage

• sessionStorage

• alert()

• Fetch API (built-in)

• CSS / HTML access

Node.js provides:

• fs (File system)

• http (Create servers)

• path

• os

• crypto

• Access to local machine resources

Browser cannot access:
❌ File System directly
❌ OS commands
❌ Server creation

Node.js cannot access:
❌ DOM
❌ window
❌ alert

4. Module System

Browser:

Uses ES Modules:

Node.js:

Uses:

✔ CommonJS (require)
✔ ES Modules (import)

5. Execution Environment

6. Event Loop Differences

Both use event loops, but:

Browser:

• Handles UI events

• Rendering tasks

• Animation frames

Node.js:

• Handles I/O operations

• File system

• Network requests

• Timers

Node.js is optimized for server-side performance.

7. NPM vs Browser Libraries

Browser:

• Uses script tags

• Uses CDN links

• Uses bundlers (Webpack, Vite, Parcel)

Node.js:

• Uses NPM packages

Example:

8. Security Model

Browser:

Very strict — cannot access computer files (for user safety).

Node.js:

Full access to:

• System files

• Network

• Processes

So it must be used carefully.

 Quick Summary: Node.js vs Browser