This post was contributed by Chengzhong Wu (@legendecas), Gabriel Schulhof (@gabrielschulhof) Jim Schlight (@jimschlight), Kevin Eady Michael Dawson (@mhdawson1), Nicola Del Gobbo (@NickNaso)

Introduction

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.

Image for post
Image for post

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.

When we started working on N-API back in 2016 (the original proposal is 12 Dec 2016) we knew it was going to be a long journey. There are many native packages in the ecosystem and we understood the transition would take quite some time. …


This blog was written by Bethany Griggs, with additional contributions from the Node.js Technical Steering Committee.

Image for post
Image for post

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.

Image for post
Image for post

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:
https://medium.com/@nodejs/call-to-action-accelerating-node-js-growth-e4862bee2919.

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.

It’s been almost 2 years and we’ve been working on a number of initiatives which you can learn more about through the issues in the package-maintenance repo. Things never move quite as fast as we’d like, but we are making progress on a number of different areas. …


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.

Image for post
Image for post
Photo by Miguel Á. Padriñán from Pexels

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 use Node.js …


Image for post
Image for post

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.

Image for post
Image for post
Photo by Donny Jiang on Unsplash

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 on the mentoring topics. Now, in addition to getting help making code commits, mentees may also learn to contribute to a team through working groups and initiatives. This will provide opportunities for people who have little or no coding experience to participate in the program. …


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.

Image for post
Image for post

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 then promoted to Long-term Support (LTS) in October 2020. As always, corporate users should wait to upgrade their production deployments until October when Node.js is promoted to LTS. However, now is the best time to start testing applications with Node.js …


This post is written by Shelley Vohr and originally appeared on the Node.js website blog.

Image for post
Image for post

The Node.js project will be adjusting its release cadence in response to adjusted work schedules.

The stability and reliability of our release lines is tantamount, and as we respond to the shifting situation around us, and the global pandemic, we feel that Node.js users will be more effectively served by this new schedule. Updates to individual release lines are detailed below.

v10.x

The next planned release of v10.x will now be on 2020-04-07.

The Maintenance date for v10.x has been pushed back to 2020-05-19, and there may now be another Semver-Patch release for the v10.x


Supporting the many flavors of JavaScript

Contributed by Benjamin Coe, who works on JavaScript client libraries at Google, is a collaborator on Node.js, and was the third engineer at npm, Inc.

Image for post
Image for post
Photo by Soloman Soh from Pexels

Of the 21,717 respondents to the 2019 State of JavaScript Survey, ~60% said that they spend time working in an alternate flavor of JavaScript, this is up from ~21% in 2016. Increasingly, when someone writes JavaScript, they’re actually writing an abstraction that compiles to JavaScript.

These abstractions offer a variety of benefits: for instance the type safety introduced by Flow and TypeScript, or the functional programming paradigm introduced by ClojureScript. However, we are also faced with a challenge. Node.js, developed in 2009, didn’t anticipate the modern world of transpilers. And so alternate flavors of JavaScript present a disadvantage in terms of observability. …


This post was written by Joel Chen with help from other members of the Node.js package maintenance team.

Image for post
Image for post
Photo by Engin Akyurt via Pexels.

Introduction

In the node.js package maintenance working group, one of the topics we’ve been discussing is about what files to include or exclude when publishing npm packages.

In general, a package’s original directory could contain other meta files that may or may not be needed in published form. These files are either OS specific or config files for the development tools used for the package.

Some common meta files are:

  • coverage, .nyc_output - coverage output for istanbul and nyc
  • .idea, .vscode - configs for IDE or…

About

Node.js

Node.js is a collaborative open source project dedicated to building and supporting the Node.js platform. https://nodejs.org/en/

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store