OpenJS Foundation Cross Project Council Meeting Scheduled for May 20th

By Announcements

The OpenJS Foundation is excited to be having its inaugural Cross Project Council (CPC) meeting on May 20th at 2 pm ET.

As part of the new OpenJS Foundation’s bylaws, the Cross Project Council (CPC) has been chartered to serve as the primary governing body for programs and regular support of Foundation projects. For example, it will be responsible for things like infrastructure, travel assistance, Code of Conduct support, accepting new projects into the Foundation, and mentorship programs to name a few. It will also be responsible for electing representatives to the OpenJS Foundation board of directors.

Anyone who’d like to get involved is welcome to attend CPC meetings and volunteer to participate in tasks, actions, and efforts. The CPC will make decisions using a consensus-seeking model so while there may be a few areas where actual voting happens, the majority of the work will be decided by the people who are involved in the work whether they are elected “Voting Members” of the CPC or interested and engaged people from the community.

If you’d like more info/context on the governance of the OpenJS Foundation, please reach out to or follow this repo.

How is the CPC Organized?
With inclusivity and maximum opportunity for community participation in mind, the CPC has three types of participants:  Observers, Regular Members, and Voting Members.

Observers are free to attend meetings and participate in the work of the CPC as well as the consensus-seeking process.

Regular members
Regular members have made a commitment to be involved in an ongoing manner and take on roles and responsibilities as outlined below. A Regular member is implied when a membership type is not specified. Anyone who has been a member of one of the projects under the OpenJS Foundation for at least three months may request to become a Regular member by opening a PR to add themselves to the list of regular members. Regular members remain for as long as they are active within the work of the CPC. Regular members who have not been active in GitHub, participated in meetings, or other work of the CPC for 3 months may be removed from the list of Regular members. In addition, a Regular CPC member can be removed by voluntary resignation, or by a standard CPC motion.

Voting members
Voting members are nominated in one of a few different ways before being ratified by the existing CPC Voting members.  Each Impact project is entitled to nominate two representatives. Projects in the Growth and At-Large stage will be entitled to nominate two additional Voting members.  Finally up to two Voting members may be nominated by a vote of the Regular members.

Initially, all nominated individuals from the Growth and At-Large group will become voting members, to help with the amount of work needed to bootstrap the organization.  In future election cycles, there will be two representatives for Growth & At Large projects, per the charter.

Voting members are expected to make a time commitment which allows them to be responsive to CPC business, participate regularly in meetings and to participate in all voting matters (either by voting or specifically abstaining). They are also expected to enable and support Regular CPC members by providing leadership, interacting with the board and Foundation staff, and to generally help keep things moving. Voting members serve for a term of one year.

The CPC will meet regularly, with the public portion of CPC discussions and meetings open to all observers and members.

Our newly elected CPC Voting Member representatives are listed below:

Impact Project Representative Appointments

Growth & At Large Nominees

All are welcome to attend CPC meetings. If you are interested, please head over to on May 20 at 2 pm ET.

If you have any questions, please reach out to

Introducing Node.js 12

By Announcements

We are excited to announce Node.js 12 today. Highlighted updates and features include faster startup and better default heap limits, updates to V8, TLS, llhttp, new features including diagnostic report, bundled heap dump capability and updates to Worker Threads, N-API and ES6 module support and more. The Node.js 12 release replaces version 11 in our current release line. The Node.js release line will become a Node.js Long Term Support (LTS) release in Oct 2019 (more details on LTS strategy here).

V8 Gets an Upgrade: V8 update to V8 7.4
As always a new version of the V8 JavaScript engine brings performance tweaks and improvements as well as keeping Node.js up with the ongoing improvements in the language and runtime. Highlights include:

Read more about V8 at their official blog.

Hello TLS 1.3
Node.js 12 is introducing TLS1.3 support and making it the default max protocol, while also supporting CLI/NODE_OPTIONS switches to disable it if necessary. TLS1.3 is a major update to the TLS protocol, with many security enhancements and should be used over TLS1.2 whenever possible.

TLS1.3 is different enough that even though the OpenSSL APIs are technically API/ABI compatible when TLS1.3 is negotiated, changes in the timing of protocol records and of callbacks broke assumptions hard-coded into the ‘tls’ module. This change introduces no API incompatibilities when TLS1.2 is negotiated. It is the intention that it be backported to current and LTS release lines with the default maximum TLS protocol reset to ‘TLSv1.2’. This will allow users of those lines to explicitly enable TLS1.3 if they want.  If you want to read more you can check out these related articles:,

Properly configure default heap limits
This update will configure the JavaScript heap size based on available memory instead of using defaults that were set by V8 for use with browsers. In previous releases, unless configured, V8 defaulted to limiting the max heap size to 700 MB or 1400MB on 32 and 64-bit platforms respectively.  Configuring the heap size based on available memory ensures that Node.js does not try to use more memory than is available and terminating when its memory is exhausted.

This is particularly useful when processing large data-sets. As before, it will still be possible to set –max-old-space-size to use a different limit if the default is not appropriate for your application.

Switch default http parser to llhttp
Node.js 12 will also switch the default parser to llhttp. This will be beneficial in that it will make testing and comparing the new llhttp-based implementation easier. First introduced as llhttp experimental in v11.2.0, llhttp will be taken out of experimental in this release.

Making Native Modules Easier – progress continues
Node.js 12 continues the trend of making building and supporting native modules easier. Changes include better support for native modules in combination with Worker threads, as well as N-API ( version 4 (which has also been backported to 8.x and 10.x) which makes it easier to use your own threads for native asynchronous functions. You can read more about this and how you can leverage it in your modules in this great article here:

Worker Threads
Worker Threads (, while not new in this release, are still seeing progress. The use of Workers Threads no longer requires the use of a flag and they are progressing well towards moving out of experimental.  While Node.js already performs well with the single-threaded event loop, there are some use-cases where additional threads can be leveraged for better results. We’d like you to try them out and let us know what use cases you have where they are helpful.  For a quick introduction check out this great article:

Diagnostic Reports
Node.js 12 brings with it a new experimental feature “Diagnostic report.”  This allows you to generate a report on demand or when certain events occur.  This report contains information that can be useful to help diagnose problems in production including crashes, slow performance, memory leaks, high CPU usage, unexpected errors and more.  You can read more about it in this great article:

Heap Dumps
If you ever needed to generate heap dumps in order to investigate memory issues but were slowed down by having to install a new module into production, the good news is that Node.js 12 brings integrated heap dump capability out of the box. You can check out the documentation in and to learn more.  

Startup Improvements
In Node.js 11 we shipped built-in code cache support in workers – when loading built-in libraries written in JavaScript, if the library was previously compiled on the main thread, the worker thread no longer needs to compile it from scratch but can reuse the v8 code cache generated by the main thread to speed up compilation. Similarly, the main thread can reuse the cache generated by workers. This gave a roughly 60% speedup for the startup of workers.

Now in Node.js 12 we generate the code cache for built-in libraries in advance at build time, and embed it in the binary, so in the final release, the main thread can use the code cache to start up the initial load of any built-in library written in JavaScript. This gives a ~30% speedup in startup time for the main thread.

ES6 Module Support
Node.js 12 brings an updated experimental version of support for ES6 modules. It is an important step toward a supported implementation and we’d like you to try it out and give us feedback.  For more details check out this great blog post.

New compiler and platform minimums
Node.js and V8 continue to embrace newer C++ features and take advantage of newer compiler optimizations and security enhancements. With the release of Node.js 12, the codebase now requires a minimum of GCC 6 and glibc 2.17 on platforms other than macOS and Windows. Binaries released at Node.js org use this new toolchain minimum and therefore include new compile-time performance and security enhancements.

The increment in minimum compiler and libc requirements also increments minimums in supported platforms. Platforms using glibc (most platforms other than macOS and Windows) must now include a minimum version of 2.17. Common Linux platforms compatible with this version include Enterprise Linux 7 (RHEL and CentOS), Debian 8 and Ubuntu 14.04. Binaries available from will be compatible with these systems. Users needing to compile their own binaries on systems not natively supporting GCC 6 may need to use a custom toolchain. Even though Node.js 12.0.0 may compile with older compilers, expect the Node.js 12 codebase (including V8) to rapidly adopt C++ features supported by GCC 6 during the pre-LTS timeframe.

Windows minimums remain the same as Node.js 11, requiring at least Windows 7, 2008 R2 or 2012 R2 and a minimum compiler of Visual Studio 2017. macOS users needing to compile Node.js will require a minimum of Xcode 8 and Node.js binaries made available on will only support a minimum of macOS 10.10 “Yosemite”.

Further details are available in the Node.js

Thank you!
A big thank you to everyone who made this release come together, whether you submitted a pull request, helped with our benchmarking efforts, or you were in charge of one of the release versions. We’d also like to thank the Node.js Build Working Group for ensuring we have the infrastructure to create and test releases. The release manager for Node.js 12 is Bethany Griggs. For a full list of the release team members head here. You can read more about the complete list of features here.

Node.js Foundation and JS Foundation Merge to Form OpenJS Foundation

By Announcements

Newly Formed Foundation to Accelerate Next Phase of JavaScript Ecosystem Growth

OPEN SOURCE LEADERSHIP SUMMIT, Half Moon Bay, Calif. — March 12, 2019 — The Node.js Foundation and the JS Foundation today announced they are merging to form the OpenJS Foundation.

The mission of the OpenJS Foundation is to support the healthy growth of JavaScript and web technologies by providing a neutral organization to host and sustain projects, as well as collaboratively fund activities that benefit the ecosystem as a whole. The OpenJS Foundation is made up of 31 open source JavaScript projects including Appium, Dojo, jQuery, Node.js, and webpack.

“This is an exciting step forward for the entire open source JavaScript community, as it strengthens the impact of our collective efforts under one united Foundation,” said Dave Methvin, Technical Advisory Committee Chair, JS Foundation. “A new merged Foundation is able to better serve the community and members to grow the JavaScript ecosystem from a technology and standards perspective.”

The OpenJS Foundation is supported by 30 corporate and end user members, including GoDaddy, Google, IBM, Joyent, PayPal, and Microsoft. These members recognize the interconnected nature of the JavaScript ecosystem and the importance of providing a neutral home for projects which represent significant shared value.

“OpenJS Foundation will provide improved member and community engagement by creating one, premier home for projects within the open JavaScript community to provide access to resources that enable better collaboration and sustainability,” said Mike Dolan, vice president of strategic programs, the Linux Foundation. “By creating a single vibrant home for any JavaScript project, the OpenJS Foundation is able to increase collaboration across the ecosystem.”

The JS Foundation and Node.js Foundation have coexisted independently for a number of years. Thanks to the interconnected nature of the JavaScript ecosystem, both organizations have grown continuously closer in technical collaboration including hosting a joint technical conference, Node+JS Interactive, beginning in 2018, which resulted in the largest event to date with a 25% increase in event attendance over the previous year.  

The merger process started six months ago, and included consensus gathering from the community as well as close collaboration with the Linux Foundation and the governing boards of the Node.js Foundation and the JS Foundation. Today’s announcement celebrates a turning point in this process as the new governance structure is now in place and the community will start operating under the OpenJS Foundation.

The OpenJS Foundation will eliminate operational redundancies between the two organizations, streamline the experience for companies that provide essential financial support through membership, and coordinate efforts within the JavaScript community and with affiliated standards bodies.

New members and new project proposals are welcome to join at any time.

Additional Resources

About OpenJS Foundation

The OpenJS Foundation is committed to supporting the healthy growth of the JavaScript ecosystem and web technologies by providing a neutral organization to host and sustain projects, as well as collaboratively fund activities for the benefit of the community at large. The OpenJS Foundation is made up of 29 open source JavaScript projects including Appium, Dojo, jQuery, and Node.js, and webpack and is supported by 30 corporate and end user members, including GoDaddy, Google, IBM, Joyent, PayPal, and Microsoft. These members recognize the interconnected nature of the JavaScript ecosystem and the importance of providing a central home for projects which represent significant shared value.

Node.js Foundation is a licensed mark of Node.js Foundation. Node.js is a trademark of Joyent, Inc. and is used with its permission. JS Foundation is a registered trademark of the JS Foundation.

Media Contact
Sarah Conway