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!
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:
We have renamed all of the core Fastify plugins that were prefixed with fastify-. We renamed them to be listed under the @fastify scope. For example, fastify-cookie is now @fastify/cookie. When you try to use latest version of the old pa…
Up until V8 10.0, the class field initializers had been broken in the V8 startup snapshot - a feature used by embedders like Node.js and Deno to speed up the bootstrapping of themselves or user applications.
Published · Tagged with internals Class fields have been shipped in V8 since v7.2 and private class methods have been shipped since v8.4. After the proposals reached stage 4 in 2021, work had begun to improve the support of the new class features in V8 - until then, there had been two main issues affecting their adoption:
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:
Authors: Brian Behlendorf, OpenSSF, and Robin Bender Ginn, OpenJS Foundation Today, we’re excited to announce that Node.js is the first open source community to be supported by OpenSSF’s Alpha-Omega Project.
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.
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:
Jest 28 is finally here, and it comes with some long requested features such as support for sharding a test run across multiple machines, package exports and the ability to customize the behavior of fake timers.
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.