Need to Node – Volume 4
The Node.js project is moving rapidly toward an awesome release of Node.js 10 (that’s right Node.js v10, not Node.js v0.10) and has a complement of new features shipping, plus a ton of work going into the overarching community efforts surrounding it.
Here’s a few highlights from the past week or so in Node.js, from the project’s GitHub organization:
What’s New in the Node.js Project
- Overall, the new effort around i18n has attracted quite a bit of input and attention from the international Node.js community and is picking up steam rather quickly. As discussed in the first i18n team meeting, work on the module to translate from the CrowdIn API to the Node.js repos is going to be spinning up shortly.
- The Node.js Security WG has a new public Slack team, which you can join to discuss Node.js Security and the work currently happening in the Security WG.
- The Node.js Modules Team has a PR proposing a manifesto, defining exactly what the core principles of the various stakeholders (presently around 50) feel the group should be working toward.
- The Node.js TSC is currently discussing the possibility of bringing the N-API out of experimental mode for the release of Node.js 10, and a PR has been submitted to the Node.js core repo to do exactly that.
email@example.com shipped (in addition to 2.9.1 and 2.9.0 on the same day) in the first major update to nan since November.
Awesome Articles and Resources
- A View into How Some Node.js Projects Address Security Challenges by Mike Samuel
- Maybe you don't need Rust and WASM to speed up your JS by Vyacheslav Egorov
- Serverless by the numbers: 2018 report by Andrea Passwater
One Last Thing…
Need to Node has been a fun series to work on weekly so far, scouring the community for cool new things. If you’ve got anything you’d be interested in seeing or have any awesome articles, modules, or other resources in the Node.js community, feel free to reach out to us on Twitter at @NodeSource to share - our DMs are open if you don’t want to share publicly!