VoidZero is driving the unification of the JS ecosystem

Steve Lebleu — Sat, 21 Mar 2026 13:24:38 +0000

VoidZero launch week is drawing to a close, and the world of Javascript development has just been given a significant boost. If you follow developments in build tools, you’ll know that fragmentation is rife, and that it’s difficult to stay at the cutting edge without using the best tool for each task. With the latest announcements regarding Vite, Oxlint and Vitest, Evan You team is taking a major step towards the goal of unifying everything to improve performance and simplicity.

Here are the key takeaways from this wave of updates.

Oxlint: no more trade-offs between speed and compatibility

Until now, choosing Oxlint meant sacrificing the ESLint plugin ecosystem in favour of Rust’s performance.

That is no longer the case: Oxlint has reached a major milestone with its JS Plugins Alpha.

In fact, your ESLint plugins now run in Oxlint without any modifications, with execution speeds up to 100 times faster than with ESLint. And as the folks at Void are so helpful, they’ve provided a migration tool (@oxlint/migrate) that allows for an automatic transition from your existing configuration.

Suffice to say that following the arrival of Biome.js, competition is becoming very, very fierce for ESLint, which has historically always suffered from limitations in execution, configuration and compatibility. It’s a drop-in replacement for around 80% of users, already adopted by major projects such as Preact and PostHog.

One bundler to rule them all with Vite 8 and Rolldown

This is undoubtedly the most significant architectural change. Vite 8 is moving away from the esbuild (dev) / Rollup (prod) combination in favour of Rolldown, its new bundler, which is also written in Rust.

In practical terms, what does this mean?

Firstly, a clear unification between your local build and your production build. No more surprises or inconsistencies between your environments.

Secondly, well – thanks to Rust – builds are 10 to 30 times faster than with Rollup. For example, the teams at Linear reportedly saw their build times drop from 46 seconds to 6 seconds, which is quite significant.

Finally, the bundler now natively supports tsconfig paths and decorators, and offers a new, much more flexible codeSplitting API. A breath of fresh spring air, as they say.

More stability and less “flaky tests” at Vitest side

Vitest 4.1 keeps pace with native support for Vite 8 and features designed for large-scale projects.

Anyone who has written tests for an asynchronous application knows the drill: they leak, they hang left, right and centre, and they’re often difficult to debug. Vitest now offers asynchronous leak detection to put an end once and for all to the timers that clutter up workflows.

In addition, you can now assign tags to your test suites to organise them more effectively. It’s not the most groundbreaking update, but it can be useful for large codebases.

Finally, VoidZero is already anticipating new development workflows by equipping Vitest with a “reporter agent”, an output optimised for AI coding agents.

Towards a “Zero Config” experience

The project goes beyond individual tools. The aim is to cover the entire application lifecycle to provide a complete value chain.

Vite+ (Alpha) centralises everything via a single binary called vp. It acts as a task orchestrator with a persistent cache. No need to configure ESLint, Prettier or Vitest separately! A single vite.config.ts file drives the entire toolchain.

This makes setup very simple:

vp create generates a new project
vp dev starts the development server
vp check performs linting, formatting and type checking in a single line
vp test runs tests using Vitest,
vp build creates an optimised production build,
vp run orchestrates monorepo tasks

Void, the deployment platform announced by Evan You, brings things full circle by offering an Infrastructure-as-Code approach, where the Void SDK analyses your code to automatically provision the necessary resources (DB, Auth, AI inference). And it doesn’t stop there, as the platform offers native support for the MCP protocol: developers can now not only write your code, but also autonomously set up and deploy the infrastructure on Void.

Key takeaways

The Javascript ecosystem is emerging from a (long) period of having a “scattered toolkit” to now natively integrate linting, testing, building and deployment under a single technological umbrella (Rust + Vite).

VoidZero offers a super-smooth developer experience, where performance comes as standard.

They are not the only ones heading in this direction – Biome springs to mind – but they provide a more comprehensive solution that will significantly improve business workflows and influence the ecosystem.

To find out more, you can consult the official migration guides on the VoidZero blog or explore the Vite 8 documentation.

This article has been translated from french original publication VoidZero pousse l'unification de l'écosystème Javascript

Email sending in Node.js

Steve Lebleu — Thu, 22 Feb 2024 16:34:25 +0000

As a developer, email sending is a recurent task across the projects.

Most part of time, you have to deal with open source libraries, to switch from a library to another accross the projects, with some particular implementations and / or behaviors.

As well, you can have a different need inside a same project just regarding the use case.

For example, you can still need to send an email to a developer when a particular event is fired, or send a transactionnal email to say welcome to a new user.

In the first case, a simple SMTP server can do the job internally.

In the second case, it's more efficient to rely to a web API, able to manage statistics, bouncing, DKIM, templating, ...

As well, you can need to deal with different providers at the same time. During a migration, for example.

Some months ago, I was wondering how to provide something flexible and consistent to deal with this kind of repetitive issue.

And I did it myself, because it was quite fun. 😎

All the cases described above - and some others - are covered by a light NPM package.

The main features are:

Configuration based
Agnostic appoach: same input, same output for all configurations
Formalized transactions conventions
Unlimited number of transporters inside the same project
Support of different sending modes (SMTP and web API)
Embeded view engine, stream or web API templates

There is Cliam, an agnostic and very flexible tool to deal with transactional email sending.

steve-lebleu / cliam

Agnostic transactional email sending in Node.js environment

Transactional emails with a kick

Agnostic transactional email sending in Node.js environment 💥 💪 💊

> Why ?

To improve and facilitate the implementation, flexibility and maintenance of transactional emailing tasks.

> Features

Agnostic transactional email sending using web API or SMTP server. One input, one output.
Multiple simultaneous transporters.
Configuration based, not implementation based : easy switch between different modes.
Normalized transactions events.
Securized payloads.
Customisable default templates.

> Table of contents

> Requirements

Node.js >= 18.19.0
NPM >= 10.2.3

> Getting started

Install

> npm i cliam --save

Configure

Create a .cliamrc.js module on the root of your project.

> touch .cliamrc.js

Define a minimalist configuration in .cliamrc.js newly created:

module.exports = {
  "sandbox": true,
  "transporters": [
    {
      "id": "unique-transporter-key",
      "auth": {
        "username": process

…

View on GitHub

Currently, following web api providers are supported: Mailgun, Mailjet, Brevo, Sendinblue, Sendgrid, Mandrill, Sparkpost, Mailsender and Postmark. Amazon SES and a lot of others should be integrated soon, but I prefer take the focus on some new features and to push more robustness before to embedd too much transporters.

Have a good dev, enjoy and feel free to use and to share 🚀

DEV Community: Steve Lebleu