After a few years since the first release of Undici 3 years ago, we have gathered many contributors and many new features. This little HTTP client that Matteo built as an experiment has quickly grown to be extremely stable and performant, leading the way in a renovated effort of bringing Node.js forward.
Inside the Node core team, not all collaborators are in agreement with the plan to recommend Undici instead of the default http.request() function. Read more and possibly contribute at the following issue.
I see a slight problem with the situation with the node core http client. We are getting issues reported in the issue tracker. However, there is little interest by contributors (that are familiar with the code) to look into these issues …
Fastify v3.18.0 shipped last week! It features a much-needed feature: the ability to print out all the hooks a given route has registered. We also moved back to the original proxy-addr module after we had to fork due an incompatibility. Read more at:
A good philosophy to live by at work is to “always be quitting”. No, don’t be constantly thinking of leaving your job 😱. But act as if you might leave on short notice 😎. Counterintuitively, this will make you a better engineer and open up growth opportunities. A thread 👇.
At @NearForm we are hiring for all possible roles between the EU and US. Frontend (React) Devs, Backend (Node.js) Devs, DevOps (Kubernetes, AWS, ..), Team lead and even a Client Principal. Take a look at https://t.co/cJC5yITMFc
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.