Reposted by Vladimir
just a reminder that i have github sponsors if you'd like to sponsor the OSS work i do.
i maintain quite a few projects, and contribute to many more. nobody other than these sponsors pay for that. so these help a huge amount, however small π
thanks so much to those who already did β€οΈ
i maintain quite a few projects, and contribute to many more. nobody other than these sponsors pay for that. so these help a huge amount, however small π
thanks so much to those who already did β€οΈ
Sponsor @43081j on GitHub Sponsors
Maintainer of chai, parse5, unjs, vueuse, tinylibs, & more. One of the e18e.dev leads. Core contributor to lit and modernweb.
github.com
January 11, 2026 at 9:51 PM
just a reminder that i have github sponsors if you'd like to sponsor the OSS work i do.
i maintain quite a few projects, and contribute to many more. nobody other than these sponsors pay for that. so these help a huge amount, however small π
thanks so much to those who already did β€οΈ
i maintain quite a few projects, and contribute to many more. nobody other than these sponsors pay for that. so these help a huge amount, however small π
thanks so much to those who already did β€οΈ
Reposted by Vladimir
I'd like to avoid forking Istanbuljs monorepo just for Vitest. Any istanbuljs Github organization members here who could make me a maintainer there? (@kentcdodds.com, @jasonkurian.dev π)
github.com/vitest-dev/v...
github.com/vitest-dev/v...
January 12, 2026 at 10:53 AM
I'd like to avoid forking Istanbuljs monorepo just for Vitest. Any istanbuljs Github organization members here who could make me a maintainer there? (@kentcdodds.com, @jasonkurian.dev π)
github.com/vitest-dev/v...
github.com/vitest-dev/v...
Reposted by Vladimir
Every open source community has a code of conduct. They would instantly and permanently ban harassers from their repos and chats. Yet many still push their members to X, where they can't do absolutely anything to protect them. Every day it is getting worse. I wonder where they will draw the line?
X has become the Everything App that Elon always wanted, if βeverythingβ means all the tools you need to fuck up someoneβs life, in one place. www.404media.co/grok-ai-sexu...
Grok's AI Sexual Abuse Didn't Come Out of Nowhere
With xAI's Grok generating endless semi-nude images of women and girls without their consent, it follows a years-long legacy of rampant abuse on the platform.
www.404media.co
January 11, 2026 at 7:28 PM
Every open source community has a code of conduct. They would instantly and permanently ban harassers from their repos and chats. Yet many still push their members to X, where they can't do absolutely anything to protect them. Every day it is getting worse. I wonder where they will draw the line?
Reposted by Vladimir
a measured response on Greenland from a number of NATO members
Iβm reluctant to give much attention to what I can only imagine is an incendiary misdirection from matters closer to home but π€·ββοΈ
Iβm reluctant to give much attention to what I can only imagine is an incendiary misdirection from matters closer to home but π€·ββοΈ
January 6, 2026 at 6:44 PM
a measured response on Greenland from a number of NATO members
Iβm reluctant to give much attention to what I can only imagine is an incendiary misdirection from matters closer to home but π€·ββοΈ
Iβm reluctant to give much attention to what I can only imagine is an incendiary misdirection from matters closer to home but π€·ββοΈ
Reposted by Vladimir
Reposted by Vladimir
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...
joyeecheung.github.io/blog/2025/12...
joyeecheung.github.io/blog/2025/12...
require(esm) in Node.js: from experiment to stability
More than a year ago, I set out to revive require(esm) in Node.js and landed an experimental implementation. After a lot of iteration and battle-testing, require(esm) is now unflagged across all suppo
joyeecheung.github.io
December 30, 2025 at 7:04 PM
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...
joyeecheung.github.io/blog/2025/12...
joyeecheung.github.io/blog/2025/12...
Vitest exposes a custom locator API so you *have* to abstract the locator, but you can use any selector inside (if you app depends on selectors, sure base *your* locators on it). Instead of using selectors directly in your tests
December 30, 2025 at 9:27 PM
Vitest exposes a custom locator API so you *have* to abstract the locator, but you can use any selector inside (if you app depends on selectors, sure base *your* locators on it). Instead of using selectors directly in your tests
Because the user cannot interact with the element based on the selector. By introducing selectors in your tests you introduce a βtestβ user that you really shouldnβt care about because it doesnβt exist in the real world
December 30, 2025 at 9:25 PM
Because the user cannot interact with the element based on the selector. By introducing selectors in your tests you introduce a βtestβ user that you really shouldnβt care about because it doesnβt exist in the real world
I think you meant the best thing. If you need custom locators, use vitest.dev/api/browser/...
Vitest
Next generation testing framework powered by Vite
vitest.dev
December 30, 2025 at 8:36 PM
I think you meant the best thing. If you need custom locators, use vitest.dev/api/browser/...
Reposted by Vladimir
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.
December 30, 2025 at 4:45 PM
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.
Reposted by Vladimir
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
Looking like the react compiler is now ~90% of the build times for puzzle.com
December 29, 2025 at 8:59 AM
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
Looking like the react compiler is now ~90% of the build times for puzzle.com
There is some minimal explanation at vitest.dev/guide/mockin...
By the way, Vitest also supports running tests in vm. It is mostly about isolation, not mocking though
By the way, Vitest also supports running tests in vm. It is mostly about isolation, not mocking though
Vitest
Next generation testing framework powered by Vite
vitest.dev
December 24, 2025 at 11:10 PM
There is some minimal explanation at vitest.dev/guide/mockin...
By the way, Vitest also supports running tests in vm. It is mostly about isolation, not mocking though
By the way, Vitest also supports running tests in vm. It is mostly about isolation, not mocking though
Reposted by Vladimir
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.
Wikipedia is built by humans.
Every day, volunteers from all over the world add to the sum of all human knowledge. One edit, one citation, one byte of data at a time.
Every day, volunteers from all over the world add to the sum of all human knowledge. One edit, one citation, one byte of data at a time.
December 22, 2025 at 8:54 PM
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.
Reposted by Vladimir
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...
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...
Using Vitest with An Angular Project | Analog
Vitest can be added to _any_ existing Angular project with a few steps.
analogjs.org
December 22, 2025 at 4:52 PM
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...
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...
As a note, vitestβs expect exposes assert method that does support it when you really want to narrow it down: expect.assert/expect.assert.deepEqual
December 22, 2025 at 6:06 PM
As a note, vitestβs expect exposes assert method that does support it when you really want to narrow it down: expect.assert/expect.assert.deepEqual
I donβt think itβs possible, the TypeScript example illustrates it perfectly. You canβt pass down a generic type to an βassertsβ keyword of another function
December 22, 2025 at 6:04 PM
I donβt think itβs possible, the TypeScript example illustrates it perfectly. You canβt pass down a generic type to an βassertsβ keyword of another function
Reposted by Vladimir
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:
Here's a before-and-after comparison:
December 16, 2025 at 5:49 PM
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:
Here's a before-and-after comparison:
Reposted by Vladimir
bless you.
you can tuna piano but you can't piano a tuna.
you can tuna piano but you can't piano a tuna.
December 12, 2025 at 1:57 PM
bless you.
you can tuna piano but you can't piano a tuna.
you can tuna piano but you can't piano a tuna.
Reposted by Vladimir
Please update (again) immediately.
Researchers have found two new vulnerabilities in React Server Components while attempting to exploit the patches last week.
These are new issues, separate from the critical CVE last week. The patch for React2Shell remains effective for the Remote Code Execution exploit.
These are new issues, separate from the critical CVE last week. The patch for React2Shell remains effective for the Remote Code Execution exploit.
December 11, 2025 at 8:51 PM
Please update (again) immediately.
So sorry to hear this, you have been a big inspiration for me and it is sad to see you how one can just end up in the wrong column of a spreadsheet π
December 10, 2025 at 2:01 PM
So sorry to hear this, you have been a big inspiration for me and it is sad to see you how one can just end up in the wrong column of a spreadsheet π
Please, leave feedback If you tried the new `fsModuleCache` experimental flag in Vitest: github.com/vitest-dev/v...
Stabilizing `fsModuleCache` Β· vitest-dev vitest Β· Discussion #9221
experimental.fsModuleCache Introduced in 4.0.11 Docs Rational: In very large projects it takes a long time to transform the whole module graph of a single test file. This can happen when one test f...
github.com
December 10, 2025 at 1:52 PM
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 π
December 8, 2025 at 1:16 PM
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 π