# History of Node.JS ## Introduction Today, JavaScript runs on servers, desktops, mobile apps, and even smart TVs. But it wasn’t always like this. Before **Node.js**, JavaScript was just a browser language. **Node.js** changed that. It gave JavaScript the power to run outside the browser and opened up a whole new world for developers. But where did it all begin? Who made it? Why was it created? Let’s explore the story of how Node.js started and made JavaScript more powerful than ever ## What is **Node.js?** Node.js is a **JavaScript runtime environment** built on Chrome’s **V8 engine** (the engine that runs JavaScript in Google Chrome). It allows developers to run JavaScript **outside the browser**—on servers, desktops, or even IoT devices like smartwatches. A few things to know about Node.js: * Built on **V8** (Chrome’s JavaScript engine) * Created in **2009** by **Ryan Dahl** * Supports **asynchronous** (non-blocking) I/O * Maintained by the **OpenJS Foundation** * Lets you **build servers, APIs, and more** using JavaScript ## **Why was Node.js Created?** Before Node.js, developers used **Apache HTTP Server** for creating web servers. Apache was powerful but had a problem—it was **blocking**. Blocking means if one user sends a request, the server waits until it’s handled before responding to the next one. This could slow things down when many users accessed a website at the same time. Ryan Dahl had a simple thought: > ***“Why can’t we make servers that don’t wait around? What if JavaScript could handle multiple requests at once, without blocking anything?”*** He imagined a system that worked like a modern restaurant — where the kitchen handles many orders in parallel instead of one at a time.  That idea led to **Node.js**. ## **The Early Days** * In **2009**, Ryan Dahl started building Node.js. * He first experimented with **SpiderMonkey**, the JavaScript engine used in Firefox. * But just **two days in**, he found it limiting. ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1752309166962/30952a6e-53f7-4cd1-a824-264cb66fcb44.png align="center") * He switched to **Google’s V8 engine**, which was **faster** and compiled JavaScript into **machine code**. * That made V8 the perfect choice for a fast and scalable JavaScript runtime. ## **From Web.js to Node.js** * Ryan originally named the project **Web.js**, because he built it to serve web pages. * But as he developed it further, he realized it had much bigger potential, it wasn’t just limited to websites. * So, he renamed it to **Node.js**, because it could act as a single “node” in a larger network of tools, services, and apps. ## **The Role of Joyent** * Ryan was working solo until a company called **Joyent** noticed his work. * Joyent offered to **fund the project** and bring it under their wing. ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1752312277495/8c860b00-26a4-4000-9877-ccf614646010.png align="center") * This helped Node.js grow faster and gain more visibility. ## **Enter NPM (Node Package Manager)** * In **2010**, Node.js got a major boost: **npm** was launched. * npm is a package manager that made it easy to install and share reusable code. * Want to work with dates? Build a web server? Connect to a database? There’s an npm package for it. * Today, **npm is the world’s largest software registry** with millions of packages, and it was one of the biggest reasons behind Node.js’s success. ## **Growing Beyond macOS & Linux** * Node.js was first built for **macOS and Linux** only. * But in **2011**, with help from **Microsoft**, Node.js got support for **Windows** too. * This made Node.js available to an even larger group of developers and allowed it to run on nearly every platform. ## **Leadership Changes** * In **2012**, Ryan stepped away from the project. * Maintenance of Node.js was taken over by **Isaac Z. Schlueter**, who also created npm. * But over time, updates to Node.js became slower, and some developers in the community felt it wasn’t evolving fast enough. ## **The io.js Fork** * In **2014**, a developer named **Fedor** forked Node.js and started a new project called **io.js**. * It was meant to move faster, with more frequent updates and **open community governance**. ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1752312944816/192379f0-9df2-421b-8951-6ba21d44e90d.png align="center") * Many developers joined io.js because they wanted quicker improvements and more transparency. ## **Reuniting the Community** * The split didn’t last long. * In **September 2015**, both teams agreed to **merge io.js and Node.js** back into a single project. * This led to the creation of the **Node.js Foundation**, an independent group responsible for maintaining Node.js going forward. ## **The OpenJS Foundation** * In **2019**, the **Node.js Foundation** merged with the **JS Foundation** (which managed other JavaScript projects like jQuery, ESLint, etc.). * The result was the **OpenJS Foundation**, a community-driven organization that now oversees Node.js and several other JavaScript projects. * Today, this foundation ensures Node.js continues to grow in a healthy and open way. ## **Summary Timeline** ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1752314879185/3037ad7b-28c6-42de-87ee-b802efc1764e.png align="center") ## **Conclusion** Node.js changed how we write JavaScript. It brought JavaScript to the server, allowed developers to write full-stack apps in one language, and made building modern tools and apps much simpler. Today, it powers tools like **Webpack**, **React CLI**, **Express**, and even backend systems for companies like Netflix, PayPal, and LinkedIn. Node.js taught the world that **JavaScript isn’t just for the browser anymore** — it’s for everywhere. ### Want More…? I write articles on [blog.devwithjay.com](https://blog.devwithjay.com) and also post development-related content on the following platforms: * [**Twitter/X**](https://x.com/devwithjay) * [**LinkedIn**](https://www.linkedin.com/in/devwithjay)