Hi Everyone! This new edition include fewer releases but a lot of linked articles. My favorite? How we implemented API Caching at scale using AWS CloudFront. Have an amazing week!
Next week NearForm will host hits first GraphQL event! Check it out, it’s free:
As you probably now, I’ll be delivering a keynote at OpenJS World in Austin in June. If you plan to join, it’s time for you to buy a ticket! The early bird ends on April 8th, so it’s a great time to save. Register at https://events.linuxfoundation.org/openjs-world/.
Early bird tickets for OpenJS World will be available up to April 8th
The new release of Undici includes a breaking change in the form of an error code change, as well as a few improvements in fetch and mocks! Check it out:
I very often complain about Jest being too intrusive - your tests are not running on Node.js APIs but Jest’s - that’s why I’m thrilled by the work of Nicolo that build an alternative runner for Jest that does not virtualize the host environment. This comes with its own caveats but it’s great:
A Jest runner that runs tests directly in bare Node.js, without virtualizing the environment. This approach is wasy faster than the default Jest runner (it more than doubled the speed of Babel’s tests suite) and has complete support for the Node.js ESM implementation.
React turns v18! I’m thrilled to see the work done by the React team to implement Suspense for streaming SSR applications, enabling new architectures and better user experiences, check it out:
React 18 is now available on npm! In our last post, we shared step-by-step instructions for upgrading your app to React 18. In this post, we’ll give an overview of what’s new in React 18, and what it means for the future.
We all want to build blazingly fast applications and one of the most effective ways to speed them up is to use caching. In large web applications it’s common to adopt a Content Delivery Network (CDN).
Every few years somebody comes up with the idea of bundling the most popular JavaScript frameworks inside the browsers. TL;DR It’s really a bad idea. For a longer explanation read the following article:
When you work on a browser, you will often hear remarks along the lines of, “Why don’t you just put [popular framework] in the browser?” This is a good question — or at least one that illuminates how those who make browsers make decisions.
I’m a fan of Fly.io, a new cloud infrastructure company that is set to make building amazing software incredibly easy (compared to AWS). They were having an hard time in scaling their Consul deployment and… read up the rest if you are a fan of distributed systems like me.
Fly.io runs applications by transmogrifying Docker containers into Firecracker micro-VMs running on our hardware around the world, connected with WireGuard to a global Anycast network. Yours could be one of them!
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.
