• The release of Node.js v10 is just a week away, and will include a suite of new features including updates to errors and the formal addition of N-API.
• Beyond these new additions, I believe we will continue to see increased adoption and development of Node.js features that have been recently proposed or otherwise landed since the release Node.js 8.
• If you’d like to learn more about the new implementation of error codes in Node.js, be sure to check out Michael Dawson’s post about it here.
• While the addition of N-API won’t visibly affect the majority of users and module developers, its goal is simple: remove barriers caused by native modules when upgrading Node.js.
• That said, there hasn’t been much discourse around or a major move towards adoption of the new implementation beyond the bounds of the Node.js core team.

@palashv2: What You Can Expect From Node.js 10: #ui #javascript #react #angularjs #reactjs…

The release of Node.js v10 is just a week away, and will include a suite of new features including updates to errors and the formal addition of N-API.

Beyond these new additions, I believe we will continue to see increased adoption and development of Node.js features that have been recently proposed or otherwise landed since the release Node.js 8.

Let’s take a closer look at what we can expect from Node.js v10:Codes for Errors in Node.js 10

There’s a rather large change coming to errors in Node.js: errors will have codes that follow a consistent and repeatable scheme.

Previously, any kind of change to errors needed to be shipped in a semver major release. This became a major pain point, and is exemplified by something as trivial as wanting to correct a typo in an error, but needing to wait until the next major version of Node.js to ship.

This has the added benefit of helping normalize errors across platforms, making for a more consistent development experience no matter the operating system being used.

If you’d like to learn more about the new implementation of error codes in Node.js, be sure to check out Michael Dawson’s post about it here.

N-API: No Longer Experimental

A pull request landed last month to change the status of N-API from Experimental to Stable. While the addition of N-API won’t visibly affect the majority of users and module…