Node.js 9 is available for initial testing
Big news from the Node.js world! Node.js 8 moves into long-term support as the Node.js 9 is available for initial testing.
Lots of things are happening in the Node.js world! News comes today that Node.js 8 has been declared stable and ready for long term support. Additionally, Node.js 9 is now available for testing as part of the current release line.
Ready for production
The big news here is that Node.js 8 has moved into long-term support. This means that Node.js 8 is going to be a stable and steady release, suitable for production. Doing so should open up Node.js 8 to a wider community.
Node.js 8 came out six months ago to great acclaim. It was the biggest release yet for the Node.js community and chock full of goodies for everyone to enjoy, including npm 5.0. Additionally, the initial release delay gave Node.js time to develop a compatible version of V8 5.8.
Now, after six months of testing and use, Node.js 8 is being moved into long-term support. Here’s an infographic from the Node.js team to show the planned lifecycle of this release:
As you can see, the plan is to have Node.js 8 running until 2019 at the earliest. After all, the goal is to create a stable foundation designed to build scalable network applications. Hence, the slightly unusual release lifecycle.
What’s new about this release of Node.js 8?
Lots! This is the last chance for things to enter the Node.js 8 release, so all of the goodies that were ready have been added in. Let’s take a look at what Node.js 8 has to offer.
Other features include full support for Async / Await, as well as experimental use of HTTP/2 and ES Modules.
What’s up with Node.js 9?
Always striving forward, the Node.js Project is keeping their eyes on the horizon. And so, Node.js 9.0.0 is now available for developers who are interested in testing and experimenting the news release. Obviously, this release has a lot of very rough and ready features and is frequently updated. It’s not recommended for those who want to use Node.js in production.
The majority of the changes in Node.js 9 are the depreciation or removal of legacy APIs. Additionally, the core codebase for Node.js is slowly migrating to a new error system. Why are they migrating? Well, all of the errors thrown by Node.js will be associated with a unique code. This will allow error messages to be changed without being considered as breaking. It’ll also make user code more robust by not relying on error messages.
Where can I find it?
If you’re interested in the changes in Node.js, you can download both the long term support version 8 and the current release 9 here. If you are on Node.js 4.x or Node.js 6.x, they recommend starting the migration process onto Node.js 8.x LTS. If you’re interested in learning more about the overall Node.js strategy, head here.