Seemingly entirely recovering from a rather severe issue with the npm@next that affected a small subset of npm CLI users last week, the Node.js community is back to work both internally and externally.

Continuing the march toward Node.js 10, Node.js core is pushing out some prominent changes and the working groups and initiatives are taking charge of new efforts across the board. Here’s a few of the highlights from the past week in Node.js:

What’s New in the Node.js Project

• The Node.js Security WG is working on clarifying how and when CVEs are created for third-party modules in the Node.js and JavaScript ecosystem.
• There’s an early stage discussion in the Build WG repo, discussing the possibility of using Node.js Foundation funds and resources to help expedite response times when an outage or incident occurs - supplementing the existing volunteer work that goes into this.
• A new Community Committee initiative is kicking off, focusing on building contributor and community badges. The intent is to enable community members to get badges digitally and physically (in the form of vinyl hex stickers).
• The code coverage microsite that publishes daily code coverage results from the master branch of the nodejs/node repo broke for a few days, but has now been fixed and redeployed.
• Version 2.3.5 of readable-stream was released, a module maintained by the Node.js project.
• The Node.js Modules Team had their second meeting, in which they discussed the scope of the team and the approach they should be taking to helping Node.js with ES Modules.

Awesome Articles and Resources

• Strategic Initiatives from the Node.js Project by Michael Dawson
• Announcing Improved Scoring in Certified Modules by Eric O'Rear
• You Got This by Glitch

One Last Thing…

Need to Node has been a fun series to work on weekly so far, scouring the community for cool new things. 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!