About Node.js®
As an asynchronous event-driven JavaScript runtime, Node.js is designed to buildscalable network applications. In the following "hello world" example, manyconnections can be handled concurrently. Upon each connection, the callback isfired, but if there is no work to be done, Node.js will sleep.
const { createServer } = require('node:http');const hostname = '127.0.0.1';const port = 3000;const server = createServer((req, res) => { res.statusCode = 200; res.setHeader('Content-Type', 'text/plain'); res.end('Hello World');});server.listen(port, hostname, () => { console.log(`Server running at http://${hostname}:${port}/`);});This is in contrast to today's more common concurrency model, in which OS threadsare employed. Thread-based networking is relatively inefficient and verydifficult to use. Furthermore, users of Node.js are free from worries ofdead-locking the process, since there are no locks. Almost no function inNode.js directly performs I/O, so the process never blocks except when the I/O is performed usingsynchronous methods of Node.js standard library. Because nothing blocks, scalable systems are veryreasonable to develop in Node.js.
If some of this language is unfamiliar, there is a full article onBlocking vs. Non-Blocking.
Node.js is similar in design to, and influenced by, systems like Ruby'sEvent Machine and Python'sTwisted. Node.js takes the event model a bitfurther. It presents an event loop as a runtime construct instead of as a library. In other systems,there is always a blocking call to start the event-loop.Typically, behavior is defined through callbacks at the beginning of a script, andat the end a server is started through a blocking call likeEventMachine::run().In Node.js, there is no such start-the-event-loop call. Node.js simply enters the event loop after executing the input script. Node.jsexits the event loop when there are no more callbacks to perform. This behavioris like browser JavaScript — the event loop is hidden from the user.
HTTP is a first-class citizen in Node.js, designed with streaming and lowlatency in mind. This makes Node.js well suited for the foundation of a weblibrary or framework.
Node.js being designed without threads doesn't mean you can't takeadvantage of multiple cores in your environment. Child processes can be spawnedby using ourchild_process.fork() API, and are designed to be easy tocommunicate with. Built upon that same interface is thecluster module,which allows you to share sockets between processes to enable load balancingover your cores.
Official Node.js Resources
To ensure authenticity and security when working with Node.js, always use official sources. Avoid trusting emails,binaries, or downloads from unofficial sources.
Official Node.js Domains
For downloading Node.js binaries and accessing official documentation, use only these domains:
- nodejs.org
- nodejs.dev(Redirects tohttps://nodejs.org)
- iojs.org(Redirects tohttps://nodejs.org)
Official npm Packages
The Node.js team maintains the following official npm package scopes:
Additionally, the Node.js team maintains packages published by thenodejs-foundation npm account,though other Node.js-related packages (likeundici) may also be maintained by contributors closelytied to the project.
Using packages from the Node.js team guarantees that you are working with officially supported Node.js components.
Official GitHub Organizations
Node.js and related projects are maintained under these official GitHub organizations:
Official Communication Channels
Node.js and the OpenJS Foundation communicate through various official and community-supported channels. You can find details onhow to get involved on theGet Involved page.
Reporting Website Issues & Downtime
If you encounter issues with the Node.js website, report them at theNode.js website repository.For real-time updates on outages, visit theNode.js Status Page.