Hey Noders! Last week have been dedicated to Security work and the finalization of [email protected] as well as reading a few very interesting articles! Thanks for following along.. and let me know what you think of this issue!
I’m starting this edition of Adventures in Nodeland by reminding you to upgrade your Node.js on Wednesday 13th.. as a set of vulnerability fixes will be released for all LTS lines. I’m running point for this release train.. let’s see how it is going!
Thursday 14th of October I will speak at the Open Source Symposium by Hashnode about my early days in OSS and what made a difference!
Pino 7 is almost there!
After almost a year in development, [email protected] is ready for prime time. All known transports have been updated and shipped, ready for v7.0.0 to hit npm. If things go according to plan, I’ll ship it next week, ready for my talk on [email protected]!
Last week we shipped Mercurius v8.6.0 and v8.5.0, adding two small features to the “messenger of the gods”: Mercurius. You might wonder why two minor release in a short timeframe… I tend to release as soon as I merge a change, in a form of continuous delivery (otherwise it’s very likeky that I would forget to ship!). Check them out:
I have found the following twitter thread incredibly fascinating. I have often worked in the aftermath of “10x engineers” and I can confirm: the result of their software is full of major flaws as they leave the teams and products they have created just to not fix them.
I have been using the new release feature of GitHub for a few months now… and it’s awesome and a true time saver. I release a new version of a module each day and this help me quite significantly! Try it out!
GitHub is where developers come to learn and celebrate what’s new in open source, and where maintainers share, collaborate and celebrate their community’s work. One of the most important parts of the software development life cycle is delivering your software to those who use it.
“Facebook can’t be down, can it?”, we thought, for a second. Today at 1651 UTC, we opened an internal incident entitled “Facebook DNS lookup returning SERVFAIL” because we were worried that something was wrong with our DNS resolver 126.96.36.199.
I write about my journey as a core contributor of Node.js, as an author and a maintainer of many modules - including Fastify and Pino. In addition, I speak at conferences, and I will add links to all my talks in case you missed one.