Guides

If you've written JavaScript in a browser and wondered how the same language ends up powering servers, APIs and build tools, the answer is usually Node.js. It's one of the most important pieces of modern web development — and this guide explains what Node.js actually is, how it works, and what it's good (and bad) at.

The short definition

Node.js is a runtime that lets you run JavaScript outside the browser — on a server, your laptop, or a build machine. Before Node, JavaScript lived only inside web browsers; Node took Google Chrome's V8 JavaScript engine and wrapped it so the same language could run anywhere, with access to files, networks and the operating system. It's open-source and cross-platform.

JavaScript on the server

Its big idea was simple but far-reaching: use one language for the whole stack. A front-end developer who already knew JavaScript could now write the back end too — the server, the API, the tooling — without learning a second language. That's a large part of why Node spread so quickly, and why so much of the modern front-end toolchain (bundlers, dev servers, test runners) runs on it.

• Runs JavaScript outside the browser, using Chrome's V8 engine.
• Event-driven and non-blocking — efficient for many simultaneous connections.
• Great for APIs, real-time apps, microservices and build tooling.
• Weaker for CPU-heavy work that blocks the single main thread.
• Comes with npm, a huge registry of reusable packages.
• Open-source, cross-platform, and the base of most front-end tooling.

How it works: the event loop

Node's defining technical trait is that it's event-driven and non-blocking. Instead of dedicating one thread per request and waiting around for slow operations like reading a file or querying a database, Node uses a single main thread and an event loop: it kicks off the slow work, keeps handling other requests, and comes back when the result is ready.

This makes Node very efficient for workloads that spend most of their time waiting on input and output — web servers handling many simultaneous connections, APIs, and real-time apps. It's a different model from traditional thread-per-request servers, and it's the reason Node can handle a lot of concurrent connections on modest hardware.

What Node.js is good for (and not)

Node shines for I/O-bound work: REST and GraphQL APIs, real-time apps such as chat or live updates, microservices, and the command-line tooling that builds front-end projects. If your app mostly shuffles data between a database, a network and a browser, Node is an excellent fit.

It's a weaker choice for CPU-bound work — heavy computation like video encoding or large data crunching — because a long calculation blocks that single main thread and stalls everything else. There are ways around it (worker threads, or offloading to other services), but if raw number-crunching is your core workload, another runtime may suit better. Honest fit matters more than hype.

Node.js, npm and the ecosystem

Node comes with npm, the package manager and registry that hosts a vast library of reusable packages. This ecosystem is a huge part of Node's value — you rarely build everything from scratch — though it also means dependency management and supply-chain awareness become real responsibilities.

The honest takeaway

Node.js turned JavaScript from a browser-only language into a full-stack one, and its non-blocking model made it a natural fit for the I/O-heavy apps that dominate the modern web. It's not the right tool for everything — CPU-bound work is its weak spot — but for APIs, real-time services and front-end tooling it's a fast, well-supported default. If you already know JavaScript, Node is the shortest path to running it on a server.