Hi all. Thanks so much for your interest in the Node.js Medium Collection. We’ve decided to retire the initiative to curate Node.js content. There are many other places to get great content and we wish you well on your Node.js journey. Archived: Node.js Medium Collection was originally published in Node.js Collection on Medium, where people are continuing the conversation by highlighting and responding to this story ..read more

This blog was written by Jack Xia, with additional contributions from the Node-API working group and project collaborators. Hello everyone! The Node-API working group needs some help from the community to achieve full unit test coverage for the node-addon-api project. If you aren’t familiar with writing native C++ addons for Node.js or what we do, this blog post (https://nodejs.medium.com/building-modern-native-add-ons-for-node-js-in-2020-cd3992c68e0) and the node-addon-api Github repo (https://github.com/nodejs/node-addon-api) is a great place to start. We’ve made it one of our milestone ..read more

This blog was written by Bethany Griggs, with additional contributions from the Node.js Technical Steering Committee and project collaborators. We’re excited to announce that Node.js 17 was released today! Node.js 17 replaces Node.js 16 as our ‘current’ release line, with Node.js 16 being promoted to long-term support (LTS) next week. You can expect new releases of Node.js 17 approximately every two weeks, keeping you up to date with the latest features and changes. As an odd-numbered release line, Node.js 17 will not be promoted to LTS. You can read more about our release policy at http ..read more

This blog was written by A.J. Roberts with contributions from the Node.js Mentorship Initiative team. Thank you to everyone who has been following the Mentorship Initiative. I’ve answered your questions in the OpenJS Slack, but I haven’t shared updates as much as I’d like so I’m writing this post to let everyone know where we’ve been, where we are now, and where we’re headed. What We Learned I joined the Mentorship Initiative over 3 years ago. Back then, it was just getting started. We had a very ambitious plan to mentor every person who wanted to contribute to Node.js and help them ..read more

Hello, Node.js users! ? The Diagnostics working group is looking for feedback on what ways Node.js users are using the async_hooks API and to elaborate on exactly what about that problem makes async_hooks useful for them. We hope to build higher-level abstractions more purpose-built for the needs of our users. Unfortunately, due to async_hooks leaking internals and being a generally confusing API, we do not see a good path forward to moving async_hooks out of "experimental" status so we are seeking input on alternatives to better serve those needs. Over the years there have been sev ..read more

After a few years since the first release of Undici 3 years ago, we have gathered many contributors and many new features. This little HTTP client that Matteo built as an experiment has quickly grown to be extremely stable and performant, leading the way in a renovated effort of bringing Node.js forward. This new release brings many breaking changes both internal and external. The new website (https://undici.nodejs.org/) shows all the documentation: take your time to familiarize yourself with the new APIs. The full change is available at: https://github.com/nodejs/undici/releases/tag ..read more

The Node.js project will complete the winding down of the ecosystem vulnerability reporting program beginning the week of May 18th. This DOES NOT affect the process for reporting vulnerabilities in the Node.js project itself. Those will continue to be handled through our HackerOne program and can be reported as described in https://github.com/nodejs/node/blob/master/SECURITY.md. The Node.js project started accepting vulnerability reports for ecosystem modules in 2016 after the Node.js Security project donated its database to the project. You can read the background “We’re donating the Node Se ..read more

This post was contributed by the Node-API team. The reason for this blog post is to explain what motivated us to rename N-API to Node-API. The issue that is tracking the transition was: https://github.com/nodejs/abi-stable-node/issues/420 BackgroundYou may have noticed N-API changed to Node-API in the documentation within the Node.js project. N-API has always stood for Node-API but was often pronounced NAPI. A concern was raised, that when pronounced that way, it could be mistaken for a derogatory term. We therefore made it our goal to clarify that N-API is Node-API whenever possible wit ..read more

This post was written by the Node.js Mentorship Initiative. The Node.js Mentorship Initiative is excited to announce a new opening. We are looking to add a new mentee to our initiative. We, therefore, invite developers who are passionate about the Node.js ecosystem and are willing to learn and contribute towards its growth and development to apply to this opportunity. The Mentorship initiative prides itself in identifying specific needs of Working Groups and Initiatives within Node.js and posts applications for available opportunities. Over the past year, we have helped the Examples Initiativ ..read more

This blog was written by Bethany Griggs, with additional contributions from the Node.js Technical Steering Committee. We are excited to announce the release of Node.js 16 today! Highlights include the update of the V8 JavaScript engine to 9.0, prebuilt Apple Silicon binaries, and additional stable APIs. You can download the latest release from https://nodejs.org/en/download/current/, or use Node Version Manager on UNIX to install with nvm install 16. The Node.js blog post containing the changelog is available at https://nodejs.org/en/blog/release/v16.0.0. Initially, Node.js 16 will repla ..read more