Skip to content

History

Node.js was initially developed by Ryan Dahl. He took the V8 JavaScript engine from Google’s Chrome browser, added some APIs, wrapped it in an event loop, and launched it as an open-source product on Linux and macOS in 2009. The Windows edition arrived in 2011.

The Node Package Manager (npm) was introduced in 2010. It allowed developers to use code modules published by others in their own projects. There was no official ECMAScript module standard at the time, so Node.js and npm adopted CommonJS.

Node.js: Novice to Ninja by SitePoint

Node.js allows a developer with frontend JavaScript knowledge to leverage their skills on the backend.

Node Version Manager

Node Version Manager (nvm) is a tool that allows multiple editions of Node.js to be installed on the same Linux, macOS, or Windows WSL system. This can be practical if you’re working on two or more projects using different versions of Node.js

Choosing a Node.js Version

Install a recent release of Node.js unless you’re supporting a legacy application with specific requirements.

Even-numbered Node.js versions — such as 16, 18, and 20 — focus on stability and security with long-term support (LTS). Updates are provided for at least two years, so I recommend them for live production servers. You should install an identical version on your development machine.

Odd-numbered versions — such as 15, 17, 19 — are under active development and may have experimental features. They’re fine for development if you’re learning, experimenting, or upgrading frequently.