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.
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 get…
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 several iterations of APIs providing…
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/v4.0.0, here we list the most important parts.
A lot of people still…
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 Security Project to the Node.js Foundation.” …
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
You 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 without introducing breaking changes.
What’s changing (only in…
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.
This blog was written by Bethany Griggs, with additional contributions from the Node.js Technical Steering Committee.
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 replace Node.js 15 as our ‘Current’ release line. As per the release schedule, Node.js 16 will be the…
Training and certifications are some of the most valuable investments we can make in ourselves, to both sharpen our skills, but also to show prospective employers, and the world, that you have what it takes as a developer. Now is a great time to invest in yourself, or in your engineering team. Starting March 29 through April 9, the OpenJS Foundation, in partnership with the Linux Foundation, will be discounting all Node.js Certification and Training.
Limited offer: check out the new preview testing environment
Today, in partnership with the LF, we are rolling out a free Node.js Environment Preview beta…
TLDR; We need your help to make sure the Next 10 years of Node.js are as successful as the first. We are launching a survey, you can take it here to help us do that. To get a bit more context on why this survey is important, read on….
Node.js had a very successful first 10 years of Node.js and the project is working to make the next 10 years even better. As part of that we’ve kicked off the Next-10 effort to document what we think is important for that to happen. …
We are excited to share that the 2021 Node.js User Survey is now open. The goal of this survey is to learn more about how you are using Node.js. This is the fourth year we’ve run the Node.js User Survey and you can see the results from the last survey here.
The survey is completely anonymized and takes about 25 minutes to complete. You can start taking the survey here. The deadline to complete the survey is February 15th.
We also invite you to share the survey link social channels too — here’s a link for retweeting. The more the merrier!