This article relies too much on references to primary sources. (September 2015) (Learn how and when to remove this template message)
|Original author(s)||Ryan Dahl|
|Initial release||May 27, 2009|
11.12.0 / March 15, 2019
11.10.0 / February 14, 2019
|Operating system||Linux, macOS, Microsoft Windows, SmartOS, FreeBSD, IBM AIX|
Corporate users of Node.js software include GoDaddy, Groupon, IBM, LinkedIn, Microsoft, Netflix, PayPal, Rakuten, SAP, Voxer, Walmart, and Yahoo!.
Dahl was inspired to create Node.js after seeing a file upload progress bar on Flickr. The browser did not know how much of the file had been uploaded and had to query the Web server. Dahl desired an easier way.
Dahl criticized the limited possibilities of the most popular web server in 2009, Apache HTTP Server, to handle a lot of concurrent connections (up to 10,000 and more) and the most common way of creating code (sequential programming), when code either blocked the entire process or implied multiple execution stacks in the case of simultaneous connections.
In January 2010, a package manager was introduced for the Node.js environment called npm. The package manager makes it easier for programmers to publish and share source code of Node.js libraries and is designed to simplify installation, updating, and uninstallation of libraries.
In January 2012, Dahl stepped aside, promoting coworker and npm creator Isaac Schlueter to manage the project. In January 2014, Schlueter announced that Timothy J. Fontaine would lead the project.
In February 2015, the intent to form a neutral Node.js Foundation was announced. By June 2015, the Node.js and io.js communities voted to work together under the Node.js Foundation.
In September 2015, Node.js v0.12 and io.js v3.3 were merged back together into Node v4.0. This merge brought V8 ES6 features into Node.js and a long-term support release cycle. As of 2016, the io.js website recommends that developers switch back to Node.js and that no further releases of io.js are planned due to the merge.
Though initially the module system was based on commonjs module pattern, the recent introduction of modules in the ECMAScript specification has shifted the direction of using ECMAScript Modules in Node.js by default instead.
Node.js is primarily used to build network programs such as Web servers. The most significant difference between Node.js and PHP is that most functions in PHP block until completion (commands only execute after previous commands finish), while Node.js functions are non-blocking (commands execute concurrently or even in parallel, and use callbacks to signal completion or failure).
There are thousands of open-source libraries for Node.js, most of them hosted on the npm website. The Node.js developer community has two main mailing lists and the IRC channel #node.js on freenode. There are multiple developer conferences and events that support the Node.js community including NodeConf, Node Interactive and Node Summit as well as a number of regional events.
The open-source community has developed web frameworks to accelerate the development of applications. Such frameworks include Connect, Express.js, Socket.IO, Feathers.js, Koa.js, Hapi.js, Sails.js, Meteor, Derby, and many others. Various packages have also been created for interfacing with other languages or runtime environments such as Microsoft .NET.
Modern desktop IDEs provide editing and debugging features specifically for Node.js applications. Such IDEs include Atom, Brackets, JetBrains WebStorm, Microsoft Visual Studio (with Node.js Tools for Visual Studio, or TypeScript with Node definitions,) NetBeans, Nodeclipse Enide Studio  (Eclipse-based), and Visual Studio Code. Certain online web-based IDEs also support Node.js, such as Codeanywhere, Codenvy, Cloud9 IDE, Koding, and the visual flow editor in Node-RED.
|Release||Code name||Release date||LTS status||Active LTS start||Maintenance start||Maintenance end|
|v0.10.x||2013-03-11||Old version, no longer supported: End-of-life||-||2015-10-01||2016-10-31|
|v0.12.x||2015-02-06||Old version, no longer supported: End-of-life||-||2016-04-01||2016-12-31|
|4.x||Argon||2015-09-08||Old version, no longer supported: End-of-life||2015-10-01||2017-04-01||2018-04-30|
|6.x||Boron||2016-04-26||Older version, yet still supported: Maintenance||2016-10-18||2018-04-30||April 2019|
|8.x||Carbon||2017-05-30||Older version, yet still supported: Maintenance||2017-10-31||2019-01-01||December 2019|
|10.x||Dubnium||2018-04-24||Current stable version: Active||2018-10-30||April 2020||April 2021|
|11.x||2018-10-23||Current Release (No LTS)||N/A||June 2019|
|12.x||2019-04-23||Future release: Pending||October 2019||April 2021||April 2022|
New major releases of Node.js are cut from the GitHub master branch every six months. Even-numbered versions are cut in April and odd-numbered versions are cut in October. When a new odd version is released, the previous even version undergoes transition to Long Term Support (LTS), which gives that version 18 months of active support from the date it is designated LTS. After these 18 months expire, an LTS release receives an additional 12 months of maintenance support. An active version receives non-breaking backports of changes a few weeks after they land in the current release. A maintenance release only receives critical fixes and documentation updates. The LTS Working Group manages strategy and policy in collaboration with the Technical Steering Committee of the Node.js Foundation.
This section may be too technical for most readers to understand. Please help improve it to make it understandable to non-experts, without removing the technical details. (August 2015) (Learn how and when to remove this template message)
Node.js operates on a single thread event loop, using non-blocking I/O calls, allowing it to support tens of thousands of concurrent connections without incurring the cost of thread context switching. The design of sharing a single thread among all the requests that use the observer pattern is intended for building highly concurrent applications, where any function performing I/O must use a callback. To accommodate the single-threaded event loop, Node.js uses the libuv library—which, in turn, uses a fixed-sized thread pool that handles some of the non-blocking asynchronous I/O operations.
A thread pool handles execution of parallel tasks in Node.js. The main thread call functions post tasks to the shared task queue, which threads in the thread pool pull and execute. Inherently non-blocking system functions such as networking translate to kernel-side non-blocking sockets, while inherently blocking system functions such as file I/O run in a blocking way on their own threads. When a thread in the thread pool completes a task, it informs the main thread of this, which in turn, wakes up and executes the registered callback.
A downside of this single-threaded approach is that Node.js doesn't allow vertical scaling by increasing the number of CPU cores of the machine it is running on without using an additional module, such as cluster, StrongLoop Process Manager, or pm2. However, developers can increase the default number of threads in the libuv thread pool. The server operating system (OS) is likely to distribute these threads across multiple cores.Another problem is that long lasting computations and other CPU-bound tasks freeze the entire event-loop until completion.
Node.js uses libuv to handle asynchronous events. Libuv is an abstraction layer for network and file system functionality on both Windows and POSIX-based systems such as Linux, macOS, OSS on NonStop, and Unix.
npm is the pre-installed package manager for the Node.js server platform. It installs Node.js programs from the npm registry, organizing the installation and management of third-party Node.js programs. Packages in the npm registry can range from simple helper libraries such as Lodash to task runners such as Grunt.
Node.js registers with the operating system so the OS notifies it of connections and issues a callback. Within the Node.js runtime, each connection is a small heap allocation. Traditionally, relatively heavyweight OS processes or threads handled each connection. Node.js uses an event loop for scalability, instead of processes or threads. In contrast to other event-driven servers, Node.js's event loop does not need to be called explicitly. Instead callbacks are defined, and the server automatically enters the event loop at the end of the callback definition. Node.js exits the event loop when there are no further callbacks to be performed.
In 2015, various branches of the greater Node.js community began working under the vendor-neutral Node.js Foundation. The stated purpose of the organization "is to enable widespread adoption and help accelerate development of Node.js and other related modules through an open governance model that encourages participation, technical contribution, and a framework for long-term stewardship by an ecosystem invested in Node.js' success."
The Node.js Foundation Technical Steering Committee (TSC) is the technical governing body of the Node.js Foundation. The TSC is responsible for the core Node.js repo as well as dependent and adjacent projects. Generally the TSC delegates administration of these projects to working groups or committees. The LTS group that manages long term supported releases is one such group. Other current groups include: Website, Streams, Build, Diagnostics, i18n, Evangelism, Docker, Addon API, Benchmarking, Post-mortem, Intl, Documentation, and Testing.
In August 2017, a third of the TSC members resigned due to a dispute related to the project's code of conduct.
- MEAN (software bundle)
- Application server
- "node-v0.x-archive on GitHub". Retrieved 2 August 2014.
- "Node.js 10 ChangeLog". Retrieved 17 March 2019 – via GitHub.
- "Node.js 11 ChangeLog". Retrieved 15 February 2019 – via GitHub.
- "nodejs/node". GitHub.
- "node/LICENSE at master". GitHub. Node.js Foundation. 17 September 2018. Retrieved 17 September 2018.
- "The MIT License". Open Source Initiative. 17 September 2018. Retrieved 17 September 2018.
- Laurent Orsini (2013-11-07). "What You Need To Know About Node.js". readwrite. Archived from the original on 2013-11-07. Retrieved 2016-01-22.
- "Node.js Foundation - Node.js". Retrieved 4 July 2015.
- "Linux Foundation Collaborative Projects". Retrieved 4 July 2015.
- Why GoDaddy's Nodejitsu deal is great for Node.js, VentureBeat, February 10, 2015
- Geitgey, Adam (30 October 2013). "I-Tier: Dismantling the Monoliths". Groupon. Retrieved 30 April 2014.
- "IBM Bluemix". Retrieved 4 July 2015.
- "You'll never believe how LinkedIn built its new iPad app". VentureBeat. May 2, 2012. Retrieved May 10, 2012.
- "Blazing fast node.js: 10 performance tips from LinkedIn Mobile". Retrieved 7 April 2015.
- Baxter-Reynolds, Matthew (November 9, 2011). "Here's why you should be happy that Microsoft is embracing Node.js". London: The Guardian. Retrieved May 10, 2012.
- "WebMatrix - Front End Web Developers take note (ASP.NET, PHP, node.js and more)". Retrieved 2 August 2014.
- Node.js in Flames November 19, 2014
- "Clash of the Titans: Releasing the Kraken, NodeJS @paypal". fluentconf.com. May 28, 2013. Retrieved September 11, 2013.
- "All such companies and their products in which Node.js is used". Retrieved 2 August 2014.
- "SAP AppBuilder". SAP. March 10, 2014. Archived from the original on February 12, 2014. Retrieved October 10, 2018.
- "Why Walmart is using Node.js". VentureBeat. January 24, 2012. Retrieved May 10, 2012.
- "Why You Really Need (A) node.js development services". codebrahma. January 10, 2018. Retrieved January 10, 2018.
- "About Node.js, and why you should add Node.js to your skill set?". Training.com. Training.com. Retrieved 23 October 2016.
- "Netscape opens intranet attack". CNET. Retrieved 2017-04-20.
- Ryan Dahl (2010-11-09). "Joyent and Node". Google Groups. Retrieved 2015-02-05.
- Harris, Amber (April 1, 2013). "The Birth of Node: Where Did it Come From? Creator Ryan Dahl Shares the History". SiliconANGLE. Retrieved 19 December 2018.
- "PHP 7 vs Node.js? They Can Be Partners, Not Competitors For a Developer!". Retrieved 21 December 2016.
- Sams Teach Yourself Node.js in 24 Hours, Sams Publishing, 05-Sep-2012
- "Ryan Dahl at JSConf EU 2009".
- "Ryan Dahl at JSConf EU 2009 Video".
- "Earliest releases of npm". GitHub. Retrieved 27 July 2016.
- "Porting Node to Windows With Microsoft's Help". Retrieved 17 April 2016.
- Dahl, Ryan. "New gatekeeper". Retrieved 26 October 2013.
- Schlueter, Isaac (January 15, 2014). "The Next Phase of Node.js". Retrieved 21 January 2014.
- Krill, Paul (Dec 4, 2014). "Why io.js Decided to Fork Node.js". JavaWorld. Retrieved Dec 15, 2014.
- Q&A: Why io.js decided to fork Node.js, Infoworld Tech Watch
- Mikeal, Rogers (January 28, 2015). "State of io.js". Retrieved 2 February 2015.
- "Node.js Foundation Advances Community Collaboration, Announces New Members and Ratified Technical Governance". Archived from the original on 24 June 2015. Retrieved 4 July 2015.
- "Node.js Foundation Combines Node.js and io.js Into Single Codebase in New Release". Retrieved 28 Jan 2016.
- "io.js and Node.js merge". Retrieved 27 June 2015.
- Node.js for PHP Developers, O'Reilly Media, Inc., 2013
- Node.js Essentials, Packt Publishing, 10-Nov-2015
- Modules, Nodejs Website
- "How to import/export ES6 modules in Node - Wisdom Geek". Wisdom Geek. 2018-06-19. Retrieved 2018-06-20.
- "bomBora - Node.js for NonStop". Infrasoft. Retrieved 14 August 2015.
- "CoffeeScript on Node.js". O'Reilly Media, Inc. April 15, 2013. Retrieved May 17, 2015.
- "List of languages that compile to JS". Retrieved October 19, 2017.
- "Node.js's cluster module". Retrieved October 19, 2017.
- "Node.js's child_process module". Retrieved October 19, 2017.
- Express.js Guide: The Comprehensive Book on Express.js, Azat Mardan, 28-May-2014
- Edge.js bridges the gap between Node.js and .NET, TechRepublic, Tony Patton, July 1, 2014
- Node.js, WebStorm supports integration with the Node.js runtime environment, WebStorm Help
- Running and Debugging Node.js, WebStorm Help
- "Node.js Tools for Visual Studio". Retrieved 1 Feb 2016.
- soywiz/typescript-node-definitions TypeScript's typings for some popular node.js modules, GitHub
- DefinitelyTyped, GitHub
- The repository for high quality TypeScript type definitions Archived February 3, 2016, at the Wayback Machine
- ImageBoard, A Node.js + Express + MongoDB application built using TypeScript on the server, TypeScript Samples
- Krill, Paul (2015-11-10). "Node.js takes center stage in NetBeans 8.1". InfoWorld.
- Nodeclipse, Enide -- Node.JS development in Eclipse, Nodeclipse Website
- Hello Visual Studio Code (with NodeJS), Channel 9, Microsoft
- Node.js Applications with VS Code, Visual Studio Code
- "nodejs/Release". GitHub. Retrieved 2018-05-03.
- "Node 8 reschedule". Retrieved 22 January 2019.
- "Node.js w/1M concurrent connections!". caustik's blog.
- "StrongLoop Process Manager".
- "GitHub - Unitech/pm2: Production process manager for Node.js applications with a built-in load balancer". GitHub.
- Aleksander Kasiuk (22 April 2015). "On problems with threads in node.js - Future Processing".
- "PostgreSQL: Documentation: 9.4: JSON Types". www.postgresql.org. Retrieved 2016-10-20.
- About Node.js, Node.js Website
- Foundation, Node.js. "Node.js Foundation | Node.js". nodejs.org. Retrieved 2017-03-08.
- "nodejs/TSC". GitHub. Retrieved 2017-03-08.
- Foundation, Node.js. "Working Groups | Node.js". nodejs.org. Retrieved 2017-03-08.
- Whittaker, Zack, After governance breakdown, Node.js leaders fight for its survival, ZDNet, August 25, 2017
- Hughes-Croucher, Tom; Wilson, Mike (April 2012), Up and Running with Node.js (First ed.), O'Reilly Media, p. 204, ISBN 978-1-4493-9858-3
- Ornbo, George (September 2012), Sams Teach Yourself Node.js in 24 Hours (First ed.), SAMS Publishing, p. 440, ISBN 978-0-672-33595-2
- Teixeira, Pedro (October 2012), Professional Node.js (First ed.), John Wiley & Sons, p. 408, ISBN 978-1-118-22754-1
- Randal L. Schwartz and Aaron Newcomb (9 January 2013). "Episode 237: Node.js". twit.tv/show/floss-weekly (Podcast). TWiT.tv. Event occurs at 1:08:13. Retrieved 9 January 2013.
- Kurniawan, Agus (July 2012), Nodejs Programming By Example (First ed.), PE Press, p. 67
- Gackenheimer, Cory (October 2013), Node.js Recipes: A Problem-Solution Approach (First ed.), Apress, p. 376, ISBN 978-1-4302-6058-5
- Ribeiro Pereira, Caio (February 2016), Building APIs with Node.js (First ed.), Leanpub, p. 152
|Wikimedia Commons has media related to Node.js.|