Node.js vs Browser JavaScript: What's Actually Different?

Node.js vs Browser JavaScript: What's Actually Different?

JavaScript runs in both Node.js and the browser, but the environments are very different. Here is what changes.

The Global Object

In the browser, the global object is window. In Node.js, it is global. This is the first difference beginners notice.

DOM vs No DOM

Browsers have the DOM, so you can manipulate HTML elements. Node.js has no DOM. There is no document or window. You work with the file system and network instead.

Modules

Browsers use ES modules with import and export. Node.js traditionally uses CommonJS with require and module.exports, though ES modules are now supported too.

Built-in Modules

Node.js has built-in modules like fs, http, path, and crypto. Browsers do not have these. Browsers have fetch, localStorage, and the DOM, which Node.js does not have.

The Runtime

Browsers run JavaScript in a sandbox for the user. Node.js runs JavaScript with full system access, including the file system, network, and processes. This is a fundamental difference in trust and capability.

The Event Loop

Both have event loops, but they differ. Node.js's event loop is powered by libuv and is more complex, with timers, pending callbacks, idle, poll, check, and close callbacks phases.

The Takeaway

Node.js and browser JavaScript share the language but differ in globals, DOM access, modules, built-in APIs, runtime access, and the event loop. Understanding these differences is key to writing backend JavaScript.