days
-3
-9
hours
-1
-3
minutes
-5
-8
seconds
-4
-5
search
JAX Developers Puzzle deadline approaching: Play for a chance to win a complimentary JAX London 2018 ticket!
This will be the new stable release line

Node.js 10 is here!

Jane Elizabeth
Node.js 10
© Shutterstock / NSC Photography

Node.js 10 is here! We take a look at all the changes it has in store for developers, including increased stability, cryptographic support, and other performance improvements!

Node.js 10 is here! This release line is all about incremental changes and stability. Node.js 10 is actually the seventh major release from the Node.js Foundation and it’s slated to become the next stable release. Big goals for this version include stability, performance, and reliability for all Node users.

At the same time, it comes the time in every release version’s life when it is no longer supported. And for Node.js 4, that time is now. (If you’re still using Node.js 4, you really should upgrade.)

So, what’s in the release? Lots of things. To start, it comes with the experimental release of Node-ChakraCore, making it easier for developers to use the JavaScript engine and take advantage of Time Travel debugging. This, by the way, lets developers find errors before it screws up the source code. Who needs a time turner when you’ve got this on standby?

N-API

Node.js 10.x is going to be the Active Long Term Support version, so it stands to reason that they’re really interested in putting out a stable version for everyone to rely on. One way they’re doing this is with N-API, the ABI stable module APIs, as an officially supported API layer.

N-API lowers the maintenance costs for native modules. It also lowers the amount of friction for upgrading Node.js in production deployments. No more module breakage! To make things better, N-API is being ported backwards into version 8.x and 6.x for everyone to be safe.

SEE MORE: The road ahead for Node.js

Improved JavaScript language capabilities

Language changes are always scary. But this should be relatively painless for Node.js fans. Let’s take a look at some of the big ones:

  • prototype.toString() now returns exact slices of source code text, including whitespace and comments.
  • The catch clause of try statements doesn’t need a parameter any more
  • Line separator (U+2028) and paragraph separator (U+2029) symbols are now allowed in string literals, matching JSON.
  • V8 now implements String.prototype.trim(), String.prototype.trimStart(), and String.prototype.trimEnd().

The whole list of changed features can be found here.

Cryptographic support

Node.js wants to make it easier for you to keep things secret and keep them safe. This is the first release line to include OpenSSL 1.x. Recent work done by the OpenSSL team and the Core Infrastructure Initiative has made it possible for Node to really take advantage of everything OpenSSL has to offer. This includes the ChaCha20 cipher and Polu1305 authenticator.

By moving to OpenSSL 1.1.0, Node.js has made it easier to upgrade to future OpenSSL versions. Node developers will be able to be secure while using the gold-standard of encrypted communications on the web.

SEE MORE: How the Node.js framework builds and delivers scalable architectur

Performance improvements

Lots to go over here! Applications built with Node.js should be able to take advantage of the promise, async generator, and array performance improvements. In particularly, the improvements here will close the gaps between desugarded promise chains and async functions.

Async functions and async generators are priorities for the V8 team, so there should be a steady stream of improvements in future released.

Get Node.js 10

Interested in upgrading your copy of Node? Head on over to the Node.js Foundation for the latest release version, as well as more information about all the upgrades, commits, and changes in this version.

Author
Jane Elizabeth
Jane Elizabeth is an assistant editor for JAXenter.com.

Leave a Reply

Be the First to Comment!

avatar
400
  Subscribe  
Notify of