We’ve had a bit of a lull in the week leading up to a security release, with release of Node.js v10 and EOL of Node.js v4 fast approaching. The project continues to chug away at continued development, and several major changes coming shortly.

Here’s a recap of some of the highlights from the last week in Node.js:

What’s New in the Node.js Project

• There’s an ongoing discussion in the Security WG about having a machine-readable resource that can tell end-users and developers the current minimum secure version of Node.js on every release line.
• The Community Committee is digging deeper into its re-definition of membership and working on teasing out a definition of what it is to be a member.
• The Modules Team is discussing a new proposal by Domenic Denicola for browsers to implement package name maps, which seems to go a long way toward resolving ESM compatibility.
• The i18n Initiative is working on a continued audit of the localization groups from prior Node.js and io.js efforts.
• The User Feedback initiative will be holding a public session with JavaScript and Node.js ecosystem tooling maintainers to begin a feedback loop on how the Node.js project is doing and what it could be doing better.

Awesome Articles and Resources

• Opensource Check by Gautam Arora
• How I Organize README.md by Gleb Bahmutov
• Awesome Node.js and JavaScript Meetups in North America by Tierney Cyren
• Most common security vulnerabilities in npm static content/file servers modules by Rafal Janicki

One Last Thing…

Need to Node has been an awesome series to work on weekly so far, getting to take a weekly deep-dive into 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!