The Node community is constantly expanding and enterprises are adding it to their stacks, because they can use the same language throughout the entire stack. This year, the Node.js Foundation released the results of a survey which identified how and on which projects people use it. One thing they haven’t covered are the versions of Node.js used in projects, which we’ll do in this post. This is our our third annual analysis of Node.js versions used in projects on Semaphore’s hosted CI/CD service.

As you can see in the last year’s report, the number of projects using version 0.10 has dropped from 33% to 26%. The long-term support (LTS) maintenance period for this version ended on October 31 2017, and for version 0.12 on December 31 2016. If you’re not familiar with it, you can find the exact Node.js foundation’s release and maintenance schedule here. Second in line is version 6.0, which was released last year.

The Node.js Foundation announced that version 8.9.0 will be the first official Node.js 8 release to reach the LTS status. You can read more about it in the official announcement.

The teams that have managed to move on from the first versions are following the trend of using newer ones, which increases overall fragmentation of versions in use. It’s also important to note that, as of March, AWS Lambda supports Node.js version 6.10, and has deprecated support for 0.10.

Semaphore CI/CD continues to provide all versions mentioned in this report preinstalled on its default platform.

How do you keep up with the new Node releases?

At Semaphore, we’re on a mission to make continuous integration fast and easy. If you’re new to Semaphore, learn more about our hosted continuous integration and delivery service.