View profile

Fastify scoped modules, Node.js v18 and other Adventures in Nodeland - Issue #57

Matteo Collina
Matteo Collina
Hi Everyone! In the last two weeks I have been traveling in the South of France with my family - I really needed a break. I’ve quickly assembled this edition composed of a few important releases and a lot of interesting articles. As usual, let me know what you think!

Fastify
Many developers ask the same question when joining the Fastify community: how do we know which modules are core and which one are ecosystem? We have listened and migrated all core modules to use the @fastify scope on npm. Read more at:
Core Modules Renamed · Issue #3856 · fastify/fastify · GitHub
Following up the massive release of all core modules, the Fastify team shipped all the module updates, including fastify v3.29.0.
Pino
Pino v7.11.0 ships with full TypeScript support for transports. [email protected] ships a few improvements to help Damien implement file rotation for pino.
Node.js
Node.js v18 also fixes a few important performance problems in using class fields. Read the article Joyee wrote at
…and the longer explanation within V8:
A big news of the last two weeks has been the OpenSSF selecting Node.js for Project Alpha - they will fund the OpenJS Foundation and in turn NearForm to help improve the security of Node.js. Read more at:
OpenSSF Selects Node.js as Initial Project to Improve Supply Chain Security - Open Source Security Foundation
Undici v5.1.0 (and v5.1.1) has shipped improving fetch and mocks! Check them out.
News
Amazon Aurora is one of the game-changing tools to help developer serverless applications. The newly updated v2 enable to autoscale the capacity of the database on demand! Check out the announcement:
One of the biggest themes of the great resignation are people leaving their jobs to start new businesses. The abundance of VC capital makes this even easier. Should you?
What is Hydration? It’s the technique that makes modern frameworks be able to server-side render and reconstruct the same state in the browser, too. Read up:
Hydration is Pure Overhead
The response to this blog post is the following thread from Sebastian:
Sebastian Markbåge
Hydration in React was originally not built for SSR. It was because IE6 had a really slow DOM API but relatively fast JS strings. It was faster to concat HTML strings on the client and then "hydrate" it. This equation later changed as more refs were used and the DOM got faster.
Should you use Marko? It’s hyper-performant framework for building sites:
…and then use Solid for apps!
Jest 28 was released to support Node v18 and improving a lot of things! Note that I normally do not recommend using Jest to test your Node.js applications - however most of you use it anyway. Check it out:
Most of the time startups fails into oblivion without no explanation. It’s really good to read up Zaplib post-mortem. I find the article really interesting because it shows that JavaScript (or TypeScript) are to dominate the frontend world for a long time and will not be replaced by Wasm/Rust/AssemblyScript. Check it out:
Partners
  • This Week in React: the best of React & React Native news. Sebastien filters the noise, and you save time.
Did you enjoy this issue? Yes No
Matteo Collina
Matteo Collina @matteocollina

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.

In order to unsubscribe, click here.
If you were forwarded this newsletter and you like it, you can subscribe here.
Created with Revue by Twitter.