Need to Node – Volume 14
The past few weeks have been a flurry of activity in the world of Node.js and JavaScript, with several massive features landing in Node.js core, a few of the project’s initiatives kicking into high gear, and a suite of discussions and releases from different areas of the project.
Quite a bit of work stemmed from the Node.js Collaborator’s Summit, which happened in Berlin just prior to JSConf EU 2018–some of which will lead to successful new projects and efforts! Here's a quick recap of what's happened online in the world of Node.js since the last Need to Node:
What’s New in the Node.js Project
- An initial implementation of workers in Node.js has landed in master, helping developers offload heavy work out of the process’s event loop.
- V8 6.7 has landed on Node.js master, which introduces BigInt to Node.js.
- The i18n Initiative has officially launched its translation tooling, using CrowdIn to enable individuals who speak languages besides English to contribute to the translations effectively and smoothly.
- The Release WG is currently discussing Development Kit and Deployment Kit versions of Node.js, focusing on streamlining the size of the Node.js binaries for production deployments.
- The team from Microsoft has shipped node-chakracore@10.1.0!
- Two new versions of node-gyp have shipped, node-gyp@3.6.3 and node-gyp@3.7.0!
- A new version of llnode shipped, llnode@1.7.1.
- At the Node.js Collaborator’s Summit, a few new groups were spun up. One of which is the reliability group, focusing on making the Node.js CI more consistently reliable.
Awesome Articles, Links, and Resources
- Why JavaScript and Node.js are ruling the web - an interview with John Papa and Alessandro Segala
- The EmpireJS CFP closes on Friday!
- There’s a Cotton Bureau campaign for libuv t-shirts, which closes on the 13th!
- Massive.js - a data mapper for Node.js and PostgreSQL
One Last Thing...
If you find any awesome Node.js or JavaScript things over the next week (or beyond!), never hesitate to reach out to us on Twitter at @NodeSource to share and get it included in Need to Node - our DMs are open if you don’t want to share publicly!