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!
This blog was written by A.J. Roberts and the Node.js Mentorship Initiative team.
The Node.js Mentorship Initiative is happy to announce our next opportunity. This one is open to developers with experience in C++. You will work hand-in-hand with the N-API working group members with the eventual goal of becoming a full-fledged member of the working group.
If you’re not familiar with the working group, we recommend checking out their recent blog post.
The N-API working group has the goal of making it easier to develop native addons for Node.js and other runtimes like Electron. They have already accomplished a…
Now is a great time to invest in yourself, or in your engineering team. Starting November 30 through December 8, the OpenJS Foundation, in partnership with the Linux Foundation, will be discounting all Node.js Certification and Training. The OpenJS Certification and Training program serves to help developers in their professional development goals.
N-API provides an ABI-stable API that can be used to develop native add-ons for Node.js, simplifying the task of building and supporting such add-ons across Node.js versions.
With downloads of node-addon-api surpassing 2.5 million per week, all LTS versions of Node.js supporting N-API version 3 or higher and node.js 15.x being released with support for N-API 7, it is a good time to take a look at the progress on simplifying native add-on development for Node.js.
This blog was written by Bethany Griggs, with additional contributions from the Node.js Technical Steering Committee.
We’re excited to announce that Node.js 15 was released today. Node.js 15 replaces Node.js 14 as our ‘current’ release line, with Node.js 14 being promoted to LTS (long-term support) later this month. You can expect new releases of Node.js 15 approximately every two-weeks, keeping you up-to-date with the latest features and changes. As an odd-numbered release line, Node.js 15 will not be promoted to LTS. Please bear this in mind when using Node.js …
This blog was written by Michael Dawson with input from the Node.js package Maintenance Working Group.
A while back I talked about the formation of the Node.js package maintenance Working Group and some of the initial steps that we had in mind in terms of helping to move the ecosystem forward. You can read up on that here if you’d like:
This blog is a call to action for package maintainers in order to help in one of our initiatives and to move it forward, we need your help.
This post was written by A.A. Sobaki and the Node.js Mentorship Initiative. By the way, if you missed our last blog post, check it out here to see the latest changes to the mentorship initiative.
The Node.js Mentorship Initiative is excited to announce a new mentee opening! We’d like to invite experienced developers to apply to join the Node.js Examples Initiative.
If you’re not familiar, the Examples Initiative’s mission is to build and maintain a repository of runnable, tested Node.js examples that go beyond “hello, world!” This is an important place to find practical and real-world examples of how to…
Today, Node.js Project, an impact project of the OpenJS Foundation, handles unhandled rejections by emitting a deprecation warning to stderr. The warning shows the stack where the rejection happened, and states that in future Node.js versions unhandled rejections will result in Node.js exiting with non-zero status code. We intend to remove the deprecation warning, replacing it with a stable behavior which might be different from the one described on the deprecation warning. We’re running a survey to better understand how Node.js …
This post was written by A.J. Roberts, A.A. Sobaki, and the Node.js Mentorship Initiative Group.
A lot has happened since our last blog post ( https://medium.com/the-node-js-collection/node-js-mentorship-working-group-573dac18d8ff ). Thanks so much to everyone who’s participated in our previous rounds. We’ve learned a ton and it’s really shaped the direction of our initiative. We’re excited to fill you in on some changes since the last time.
Before we dig in, here’s a link to where we’ve got our repo set up: https://github.com/nodejs/mentorship. This will contain all updates and information in the future.
What’s Changing? First, we’re going to have a broader focus…
This blog was written by Michael Dawson and Bethany Griggs, with additional contributions from the Node.js Community Committee and the Node.js Technical Steering Committee.
We’re excited to announce that Node.js 14 was released today! The highlights in this release include improved diagnostics, an upgrade of V8, an experimental Async Local Storage API, hardening of the streams APIs, removal of the Experimental Modules warning, and the removal of some long deprecated APIs.
Node.js 14 replaces Node.js 13 as our current release line. As per the release schedule (https://github.com/nodejs/Release#release-schedule), Node.js 14 will be the `Current` release for the next 6 months, and…