Finished two retrospective blog posts on the journey of require(esm) before 2025 ends: joyeecheung.github.io/blog/2025/12... joyeecheung.github.io/blog/2025/12...

Some friction is healthy in our online interactions. You shouldn't be able to send a bug report without a reproduction. You shouldn't be able to create a PR without understanding the issue (and the solution). You should (try to) be aware of their context before replying to an unknown person online.

Had an 'upgrade to vite 8' PR running for a few weeks, and got it feature complete. Here's the rough difference in build timings for our vite projects in a monorepo from 6 -> 8. Looking like the react compiler is now ~90% of the build times for puzzle.com

More than 3GB added to English Wikipedia alone this year. Nearly 250k editors worldwide. The collaboration network Wikipedia fostered is such an incredible gift to the world.

Thanks to the @nx.dev team for keeping the support for @analogjs.org gjs and @vitest.dev t_dev alongside @angular.dev support in the latest 22.3.0 release. If you're on an older Angular project check out the guide Nx 22.3 nx.dev/blog/nx-22-3... Vitest migration guide analogjs.org/docs/feature...

npm's broken UI bugged me enough I wrote a userscript to fix them, and added some features too. Repo: github.com/bluwy/npm-us... Here's a before-and-after comparison:

bless you. you can tuna piano but you can't piano a tuna.

Please update (again) immediately.

Please, leave feedback If you tried the new `fsModuleCache` experimental flag in Vitest: github.com/vitest-dev/v...

A new milestone! @vitest.dev hit 20 million mark 🎉 Took us 4 years since the first closed 0.0.0 release on December 3d, 2021 😄

When using vite@8-beta with Vitest users no longer need to add magical '@preserve' keywords in their coverage ignore hints. Originally this work-around was needed due to esbuild's (intentional) lack of support for comment preserving. Oxc has built-in support for JS coverage tools' ignore hints.

Node excitement 😉 Congrats to @hybrist.dev on landing support for Package Imports that start with #/ 🎉 Previously this prefix was special-cased and would error. It's convenient to use it as an internal absolute path to the package root. import foo from "#/src/file.ts"

I feel the dilemma is, that I feel responsible for being friendly and welcoming to make the experience nicer for newcomers to OSS, who may not yet know the manner well. But with AI messing this up, it's really hard to tell if it's a human behind I should take care or just AI doing terrible work.

Don't even know if I should build some LLM-powered tools to fight back magic with magic, or if I should just quit altogether. Agents create the illusion that you can accomplish complicated work with simple prompts, and people become less appreciative of the hard work behind the scenes.

Vitest 4.0.15 comes with a cool experimental feature: Imports Breakdown. Every module shows how long it took to load in UI and in the VSCode extension! Pass down `--experimental.printImportBreakdown` to also see it in your terminal. vitest.dev/guide/ui.htm...

Announcing Oxfmt Alpha! 🚀 We’re excited to announce the alpha release of Oxfmt, our Rust-powered formatter. We designed Oxfmt to be easily adoptable, especially for existing Prettier users More below and in our announcement post voidzero.dev/posts/announ...

Exciting things coming to the Vitest UI reporter 👀

Want to speed up subsequent @vitest.dev runs? Then try out the new experimental file-system based cache ✨ ⋄ Caches transformed modules ⋄ Does *not* work with browser mode yet ⋄ Can be manually cleared via `vitest --clearCache` More in the docs vitest.dev/config/exper...

Merged! Vitest 4.0.14 includes a new tabbed view and slider for visual regression reports 🎉 This feature required a lot of work under the hood, including the creation of the new test artifacts API. Really curious to see how it'll be used by us and the ecosystem 👀

This describes it perfectly. When reading these LLM texts I catch myself often thinking: "what are they even trying to say?" 👀

Vitest 4.0.11 adds an experimental `fsModuleCache` flag to cache module transforms between reruns. Learn more: vitest.dev/config/exper... This is an opt-in feature, please let us know how it works for you! And example of a single test file that imports a lot of files (~1500). Almost a 50% boost!

Did you know that you can match against Standard Schemas in @vitest.dev? With the release of Vitest 4, this is possible now. No matter if you want to match your whole data or only partials against a schema and no matter which validation library is used as long as they support Standard Schema

Wrote about how our testing strategy evolved to include visual regression testing and how we can generate hundreds of tests in a handful of lines of code Spoiler: turns out high school math can be useful after all 😶‍🌫️ macarie.me/writing/when...

My first advice to junior contributors is to STOP using vibe coding for PRs. OSS is always about people more than about code. We don't need more code generated by LLM, we need more people who care.

⚡️Finally! The official statement! @vitest.dev is now the official #Angular #testing framework 💪

Vite 7.2 is out! ⚡️ 🗃️ `build.license` option 🔌 proxy + HTTP2 support 💜 and more features and fixes Don't forget to check the complete changelog at github.com/vitejs/vite/...

ECMAScript excitement 😉 Congrats to @manishearth.bsky.social on unflagging TC39 Stage 3 Temporal in V8 today. Heading for Chrome 144 🎉 By many metrics this new date-time API is the single biggest change to JS ever 🔥 V8 uses Boa's temporal_rs by @jason-williams.co.uk Kevin Ness & Manish 👍

Tip: if you want an issue solved without doing the work yourself, don't use an accusatory tone when reporting it. And don't continue to do so when a response is provided pointing you in the direction to solve it.

We raised a $12.5M Series A round, led by Accel. In this next stage, VoidZero is accelerating development on both our open-source projects and Vite+, the unified JavaScript toolchain. This is only the beginning! → voidzero.dev/posts/announ...

My talk slides are available here hiroshi-talks.vercel.app/2025-10-25/1 also with source code in github.com/hi-ogawa/talks It was a great experience to talk with many awesome folks in person! Thanks @vuefes.bsky.social for the opportunity!

Potentially coming to a @vitest.dev browser mode report near you 👀 New view for visual regression testing failures with tabs for: - diff, reference, and actual screenshots - slider to compare reference vs actual (before/after style)

Watch Jessica Sachs explain and demonstrate Vitest Browser Mode, which tests components in an actual browser instead of headless tests. Full video in comments 👇

Vitest 4 is out! - Browser Mode is Stable - Visual Regression Testing - Improved Debugging - Pool Stabilization - New APIs - Bug Fixes Stay updated with our blog post: vitest.dev/blog/vitest-4

After maintaining Tinypool for over 2 years I'm happy to see next version of Vitest dropping it. I've written some reasoning about this in the linked PR. Even though this change is significant for Vitest, I'm more confident about it than making new changes in Tinypool. github.com/vitest-dev/v...

Edinburgh castle failing to render, likely thanks to the AWS outage

VoidZero's @erus.dev talks about the upcoming @vitest.dev features including the new report API and multi-browser configuration as well as what to expect in Vitest 4 🧪 Full video in comments

First time speaking at a conference!

Watch VoidZero’s @overlookmotel.bsky.social explain how oxlint tackles JS-Rust interoperability to maintain high performance for plugins. Full video in comment 👇

Vite+ will be free for individuals, OSS, & small businesses. We plan a flat fee for startups and custom pricing for enterprises. Our goal is to capture a portion of the value Vite+ creates at scale and reinvest it into the open source projects that power Vite+.

The Unified Toolchain for the Web We are thrilled to announce Vite+: A unified, Rust-powered toolchain and drop-in upgrade for @vite_js. Read the full vision and learn about our sustainable licensing model (free for individuals, OSS & small businesses). voidzero.dev/posts/announ...

you can sponsor @e18e.dev through GitHub Sponsors or OpenCollective these funds will primarily be used for two things: - distributed to projects/individuals in the wider JS community - development of community projects/tools thanks so much to those of you who already sponsor us 💙

Vitest vscode extension now displays your console.logs inline. An example of logging in browser mode:

What an excellent group 🙌 Best part of meetups and conferences @viteconf.org

Just talked about Vite+ at @viteconf.org - check out more at viteplus.dev :) More detailed announcement on Monday!

"Let's hear it for the UN of Javascript! Vite: The Documentary is finally here. If you missed the premiere, it's OK!!! Here's the link so you can watch it again, and again and again. youtu.be/bmWQqAKLgT4 "

Not unexpected, but still disappointing 🙃

Wonder what updates are coming to your favorite testing tool? Then join @erus.dev at ViteConf and hear more about what is planned for @vitest.dev! Can't wait until tomorrow to start the conference. Join us in-person or through the free live stream at viteconf.amsterdam

What's new in ViteLand? Our September 2025 recap is out 🤯 Up to 45% faster & smaller @rolldown.rs 💻 @vitest.dev Browser Mode updates ⚓️ Performance tweaks, rules & fixes for Oxlint 🎉 Oxlint Custom JavaScript Plugins prototype ✨ Updates from the Community 👀 and more voidzero.dev/posts/whats-...

read this. I was working on an extraordinarily similar post but jake's is much better.