Monday, 23 April, 2018 UTC
Summary
It’s release week! Node.js 10 is just around the corner (with some awesome new features) and we couldn’t be more excited. Quite a bit of work is being focused on the release of Node.js 10, and the meta discussions around it. Soon we’ll be returning to normalcy, but in the meantime there’s quite a bit going on around the project.
Here’s a quick recap of some of the highlights from the last week in Node.js:
What’s New in the Node.js Project
- Work to ship Node.js 10 is nearly complete in the nodejs/node repository. There will be a final release candidate shipping the day this blog post is published (Monday April 23rd, 2018)
- The CITGM team is looking at adding support for Yarn installations within CITGM.
- A discussion was started in the Release WG around solidifying Node.js release dates even further, putting in place some specific rules and boundaries to ensure that releases happen when the project says they’re going to happen.
- The Community Committee is working through restructuring efforts around membership, and has a PR up in their core repository with the proposed changes to be worked on.
- The Docker WG is investigating speeding up the Alpine + Node.js image builds, and is seeing some interesting success with multi-stage builds already.
- Turbolizer - a
npm install-able wraper around the V8 turbolizer tool. - require-so-slow - measure the time of your
require()s - What You Can Expect from Node.js 10 - an update on what’s coming in tomorrow’s release of Node.js 10!
- Understanding the Buffer Deprecation in Node.js 10 - A deep dive into the upcoming deprecation of the Buffer constructor in Node.js 10.
- Electron is working on a free auto-updater service, and is looking for testers.
If you’ve got anything you’d be interested in seeing or have any awesome articles, modules, or other resources in the Node.js community, feel free to reach out to us on Twitter at @NodeSource to share - our DMs are open if you don’t want to share publicly!