The NodeSource Blog

Need to Node – Volume 16

This week there’s been a few pretty interesting updates on older discussions in addition to new discussions and releases that have a large and widespread impact on the Node.js platform and ecosystem – all positive, of course.

Here’s a quick recap of updates to both the old and the new from the past week:

What’s New in the Node.js Project

  • There’s a large, ongoing discussion around what "web compatibility" means and what the goals of Node.js are with having “web compatibility” for ESM in Node.js. The discussion is seemingly progressing and also building out more of what that definition actually needs to be.
  • A proposal has shipped for transparent interoperability between Node.js modules and ESM modules. As the title says, it’s a proposal and definitely subject to change – but the Modules WG is making significant progress.
  • Progress is being made on an official Docker image for Node.js that ships without npm or yarn. This effort is being taken on entirely outside of the work that’s done on Node.js core, and the Docker WG is doing a fantastic job with it.
  • An initial implementation of a JavaScript API for llnode was merged into the llnode repository, significantly lowering the barrier to entry for usage of llnode.
  • The readable-stream team has shipped the first release candidate for v3.0.0.
    • You can install today via npm install readable-stream@next! You can report bugs in the PR.
  • The User Feedback Initiative is beginning to work on building out a survey for end users around Promises. Node.js core contributors have already begun creating the survey questions.

Awesome Articles, Links, and Resources

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!