Testing framework powered by @vite_js ⚡️, brought to you by @voidzerodev | Bluesky: bsky.app/profile/vitest.dev 🦋
Bluesky
- Tweets 399
- Following 27
- Followers 32,074
- Likes 859
Pinned Tweet
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
4
162
931
103,872
Vitest 1.0 is here!
- easier to read snapshots (say goodbye to \\")
- improved coverage support
- improved typechecking support
- performance optimizations
- --project option for workspaces
- a lot of bug fixes!
github.com/vitest-dev/vitest…
9
276
1,379
134,341
Vitest 3.0 is here!
vitest.dev/blog/vitest-3
11
244
1,328
65,062
Vitest 2.0 is out!
- better Browser Mode support (still experimental)
- stability improvements (`forks` pool is now the default)
- new `blob` reporter to merge reports from different processes
- a lot of bug fixes
github.com/vitest-dev/vitest…
8
155
800
54,766
Introducing the new official Vitest VS Code extension!
Starting with version 0.6.0, the VS Code extension now supports:
- instant feedback
- .each test declaration
- test tree view
- coverage reporting
- better debugging support
- improved performance
vitest.dev/vscode
12
90
590
54,697
After 500+ commits and 100 iterations, @vitest_dev is open to everyone 🎉
It is still in development. We don't recommend migrating your current testing setups yet. But you can give it a try in new projects. Join chat.vitest.dev and get involved 🙌
github.com/vitest-dev/vitest
7
155
557
Vitest 3.2 is out!
- New Annotations API
- Scoped Fixtures
- Custom Browser Locators API
- Test Signal
- Better V8 Coverage Result
And many more features!
vitest.dev/blog/vitest-3-2.h…
5
85
554
39,651
🌟 Vitest now has an official @code extension!
👨💻 We are also excited to announce we had @zxch3n, the author of the extension, joined our team!
👇 Click the install and give it a try!
github.com/vitest-dev/vscode
2
82
530
Vitest Browser Mode is getting new powerful features! 🎉 Read our thoughts on the current state of component testing and future plans for the Browser Mode 👇
github.com/vitest-dev/vitest…
ALT Running tresjs example in Vitest Browser Mode
5
59
316
53,511
✨ Adoption milestone! After three months, @vitest_dev npm downloads represents more than 10% of @vite_js npm downloads 🤯
And we just crossed 5K Followers on Twitter 💚
Give your tests a DX boost with vitest.dev!
2
36
280
The results for State Of JS 2021 are out!
@vitest_dev is at the top in the Interest ranking 🔥
2021.stateofjs.com/libraries…
5
41
267
Vitest 1.3.0 is out!
- new onTestFinished hook
- improved handling of CLI options
- optimizer is disabled by default due to stability concerns
- better browser mode support
- persistent splitpanes sizes in UI
- bug fixes
github.com/vitest-dev/vitest…
41
265
37,273
Vitest 3.1.0 is out! ⚡
Apart from performance improvements and fixes, this release expands your test setup flexibility with new options. Check out the release notes here.
github.com/vitest-dev/vitest…
3
38
259
19,051
🎉 We are excited to announce that `eslint-plugin-vitest` is now the official `@ vitest/eslint-plugin`!
🙏 Huge thanks to the awesome work by @veritemm!
👇 Remember to migrate to the new package name:
github.com/vitest-dev/eslint…
1
32
232
14,290
Milestone: vitest crossed 10M weekly npm downloads! ⚡
ALT Graph of Vitest weekly npm downloads for the last two years. From 1.5M to 10M. 500M total npm downloads
3
9
231
19,736
There is now a @vitest_dev recipe in the new @vuejs docs!
vuejs.org/guide/scaling-up/t…
And it is recommended in the official scaffolding tool 💚
ᐳ 𝚙𝚗𝚙𝚖 𝚌𝚛𝚎𝚊𝚝𝚎 𝚟𝚞𝚎
✓ 𝙰𝚍𝚍 𝚅𝚒𝚝𝚎𝚜𝚝 𝚏𝚘𝚛 𝚄𝚗𝚒𝚝 𝚃𝚎𝚜𝚝𝚒𝚗𝚐? ... 𝚈𝚎𝚜! ⚡️
🎉 It's done! Vue 3 is now the default version and the brand new vuejs.org is live!
More details in the blog post in case you missed it: blog.vuejs.org/posts/vue-3-a…
5
40
223
Vitest now has an examples folder to help you get started: Vue, Svelte, React, Lit, RTL, Puppeteer, MSW.
Thanks to everyone that contributed to these playgrounds!
Also, we just hit 2K stars on GitHub! 🌟
github.com/vitest-dev/vitest
3
31
217
We just released v0.1.0 of Vitest!
It's identical to the last version, but this marks we start doing semver from now. You could feel more confident when trying it as you will know when there are breaking changes 🙌
33
213
Vitest 1.6.0 is out!
- performance improvements to the "forks" pool
- `--standalone` flag to start Vitest in watch mode without running tests
- `--compare` flag to compare benchmark results
- new options to inject scripts in browser mode
- bug fixes
github.com/vitest-dev/vitest…
1
23
210
28,844
Vitest 1.4.0 is out! We also rewrote our VSCode extension to use Vitest API directly which greatly improves the developer experience. Try out the pre-release version here: vitest.dev/vscode
github.com/vitest-dev/vitest…
4
29
207
20,963
Vitest is production-ready 👀
Used Vitest so smoothly that I almost forgot it is not production-ready 😂 @vitest_dev when is v1.0.0 estimated to be ready? 🥰🥰
#vuenation
10
13
181
50,417
In Vitest 1.0 you can more easily provide data from the main thread to your test files by using provide/inject API: vitest.dev/config/#globalset…
ALT // Inside the globalSetup file import type { GlobalSetupContext } from 'vitest/node' declare module 'vitest' { interface ProvidedContext { dbUrl: string } } export default function setup({ provide }: GlobalSetupContext) { provide('dbUrl', 'http://localhost:1234') } // Inside the test file import { inject } from 'vitest' const url = inject('dbUrl')
17
179
29,451
Vitest 1.0.3 fixes severe performance regression during the watch mode introduced in 1.0. It is highly recommended to upgrade.
github.com/vitest-dev/vitest…
16
176
15,803
Thank you for developing this extension, and we wish you good luck with your startup! 💚
I left the @vitest_dev team because I couldn't actively maintain the Vitest VSCode extension. It's now maintained directly by core team members.
The extension is now transferred to the Vitest publisher. You can migrate in VSCode.
The future of the extension is promising 🔥
1
6
171
16,281
💚⚡️
> Storybook 8 also integrates Vite’s testing package, Vitest, as part of our new framework: storybook/test. This new testing framework replaces two previous packages, enables the use of Vitest’s spy and expect, and has a smaller installation footprint.
Storybook 8 is here! 🥳
📸 Visual Tests addon
⚛️ React Server Component support
🎛️ Upgraded Vue & React control autogeneration
⚡️ Rearchitected @vite_js support + Vite 5
✨ New UI on desktop and mobile
💯 8,865 commits, 773 PRs, 218 contributors
storybook.js.org/blog/storyb…
14
155
14,469
We've released patches for a critical security vulnerability. We strongly encourage projects to upgrade to versions 1.6.1, 2.1.9, or 3.0.5 as soon as possible.
github.com/vitest-dev/vitest…
2
38
166
23,977
Vitest 1.5.0 is out!
- improved error messages for toMatchObject
- improvements to v8 coverage reporting
- custom diff truncation options
- better --inspect support
- bug fixes
github.com/vitest-dev/vitest…
2
22
158
17,797
Help us gather more feedback for the Vitest 2.0: github.com/vitest-dev/vitest…
2
21
150
30,882
Vitest v0.25.0 is just landed!
✅ Builtin typechecking with expectTypeOf!
🐞 onTestFailed hook to capture internal closure
🗺️ Better sourcemap support
Big shout out to @sheremet_va who is leading the development of Vitest with many great features!
github.com/vitest-dev/vitest…
22
145
Congrats to our team members @sheremet_va and @hiroshi_18181 for joining @voidzerodev to work on Vitest and Vite full-time! 🎉
We are deeply grateful for all our special sponsors who provide full-time support to our team members! Let's make Vitest even better together! 💛
ALT Vitest is free and open source, made possible by wonderful sponsors. Special Sponsors: VoidZero, NuxtLabs, StackBlitz, Zammad
7
131
15,408
Yesterday's opening of vitest.dev has been so encouraging!
You gifted us with 1K stars on GitHub 🌟
2K+ followers are now part of our journey on Twitter
And we are 250 devs in chat.vitest.dev 🛠️
Thank y'all! 💛
github.com/vitest-dev/vitest
5
21
133
Did you know that you can selectively silence any log statement in #vitest?
ALT export default defineConfig({ test: { onConsoleLog(log) { if (log.includes('Not implemented: navigation')) return false }, } })
3
9
129
14,107
Vitest 1.1.2 fixes severe performance regression introduced back in 0.34.0 among other fixes! If you are using jsdom/happy-dom you should see a noticeable speed improvement depending on the number of test files you have.
github.com/vitest-dev/vitest…
18
128
11,796
We just released Vitest v0.10! 🚀
📞 (done)=>{} callback style has deprecated in favor of promise / async
🧹 Cleanup callbacks for `beforeAll` and `beforeEach`
💡 Extendable context for each test!
📣 Custom reporter from path / package
Changelog here
github.com/vitest-dev/vitest…
1
15
126
We are thinking about adding "type tests" for @typescript directly!
Check out the RFC and let us know what you think!
github.com/vitest-dev/vitest…
1
15
114
Vitest crossed 3.5M weekly npm downloads! 1/3 of Vite's downloads now. We're not stopping until having more installs than Vite ✅
10M weekly npm downloads! ⚡️
Vite downloads are a reflection of the constant growth of a lot of projects! Kudos to all the teams in the ecosystem that keep working together to improve our shared base 💜
ALT A graph showing the weekly npm downloads of the vite package since 2020 until January 21, 2024, where vite crossed the 10 million mark
1
7
110
17,652
Check out "Vitest and The Anatomy of a Test Runner", by @_jessicasachs, part of @ThisDotMedia's Vue World Tour (also featuring awesome talks by @Zelig880 and @evanyou) 💚
⚡️ piped.video/watch?v=Pvy2ZlKu…
2
18
110
Hey Rolldown! 🙌
Hello world!
Rolldown is now open source on GitHub: github.com/rolldown-rs/rolld…
1
100
6,410
Our documentation is now available in Chinese!
Thanks to the hard work of @huchengye and the community 🙌
Vitest 中文文档已上线！
cn.vitest.dev/
2
13
102
> Unit and E2E tests have been migrated to @vitest_dev, providing a faster and more stable DX. This move also works as dogfooding for an important infrastructure project in the ecosystem. ⚡️
vitejs.dev/blog/announcing-v…
2
12
84
✅ 10k followers at @vitest_dev 🎉
Thanks to the testing community for your support! If you aren't there yet, join us at chat.vitest.dev to keep improving together our tests DX ⚡️💚
ALT An image showing the Vitest logo and below it "10k Followers! @vitest_dev"
2
83
Very easy answer, bun doesn't isolate your tests. Vitest does this by default, but it can be disabled with `--no-isolate` flag. Docs: vitest.dev/guide/improving-p…
1
5
80
5,794
✅ State of JS 2022: Vitest Interest and Retention are at the top of the Testing category. Usage raised from 2.7% to 14.1% and Awareness doubled to 46.9%!
Special shoutout to @sheremet_va for the massive maintenance effort done during the last year ❤️
2022.stateofjs.com/libraries…
1
14
79
11,743
We're going to be mainly active at @bluesky from now on. Follow us there for the latest @vitest_dev updates 👋
ALT A code snippet: import { expect, test } from 'vitest', test compare platforms, expect butterfly emoji to be greater than X emoji
4
7
72
10,695
Have you tried @vitest_dev in @stackblitz yet?
Modify a test to make it fail and see Vite's HMR kicking in for your tests ⚡️
Props to @elmd_ for his responsiveness in helping us get Vitest working smoothly in WebContainers 🙌
stackblitz.com/fork/node-8ho…
13
72
👋 We just created our Open Collective page! And the GitHub Sponsor profile is also in progress
💖 If you enjoy using Vitest, sponsor us or ask your company to sponsor. Help us make Vitest sustainable and getting better! Thank you! 🙏
opencollective.com/vitest
1
13
63
14,944
One of the main reasons why your tests might run slower is relying on barrel files.
New post: The barrel file debacle 🪂
How innocent looking code makes your tools slow, often by as much as 60-80%. Test runners and many import cycle detection tools are most affected by this.
marvinh.dev/blog/speeding-up…
1
8
64
22,295
PSA: @sheremet_va is cooking something HUGE! 🔥
github.com/vitest-dev/vitest…
3
7
54
25,371
Remix Stacks testing is powered by @vitest_dev 🔥
For the first, Remix has three stacks to choose from. They include so many useful features that giving them a descriptive name wouldn't make sense, so we name them after music genres!
Included: Ready-for-production hosting configuration, Databases, Auth, testing, & CI pipelines!
ALT Three browser tabs showing deployed versions of Remix stacks. Grunge Stack, Indie Stack, and Blues Stack
ALT Three browser tabs showing github repos for the Grunge Stack, Indie Stack, and Blues Stack
6
55
✅ expect( daysTo(@ViteConf) ).toBe( 11 )
Don't miss @sheremet_va's talk!
✨ Vitest, testing DX reimagined
viteconf.org/ecosystem/vites…
7
52
> We also moved the unit tests from Karma + Jasmine to @vitest_dev, resulting in greatly improved maintenance DX and CI stability. ⚡️💚
3
50
First answer on our "Give us feedback!" thread 💛
There are now 16 contributors in the Vitest private repo. And new folks are getting involved every day.
@vitest_dev is moving fast ⚡️
5
49
What’s Up With Vitest? @syntaxfm 💚
syntax.fm/show/443/what-s-up…
1
8
43
See y'all at @ViteConf 2023! 🎉
viteconf.org/23/ecosystem/vi…
5
42
4,705
The Vitest community will be at @ViteConf 24! 💛💚
viteconf.org/24/ecosystem/vi…
1
4
36
3,265
Bjorn's work on Vite also helps Vitest tremendously!
Finally got GitHub Sponsors setup! You can sponsor me to support my open source work on Vite, Svelte, and Astro 💖 github.com/sponsors/bluwy
2
31
10,130
Our team has now expanded: @antfu7, @patak_dev, @Aslemammad, and @sheremet_va, and there are 19 contributors in github.com/vitest-dev/vitest
We'd like to thank all our sponsors, that are helping us build Vitest 💛💚
1
2
33
So, here we go! Start at vitest.dev, and re-ignite your passion for testing. Collaborate with us at GitHub and join our community. Let's build Vitest together. It's time for a native @vite_js Test Runner ⚡️
1
2
34
There is almost a VitestConf this year! @sheremet_va, @_jessicasachs, @ari_perkkio, and @mmkalmmkal will speak at ViteConf 24 🎉
We're thrilled to share the ViteConf 24 Speakers lineup!
On October 3rd & 4rd, get ready to learn from the builders pushing modern web development forward ⚡️
Register for free today and invite your communities to the party! 🎉
5
29
5,985
The full changelog is available at github.com/vitest-dev/vitest…
7
2,063
👀
In preparation for 2.7, picking up the Vue 2 Flow to TS PR from @pikax_dev …
Build is working, and managed to get some tests running in vitest 👀
1
18
We're grateful to everyone that has contributed to @vitest_dev! Also, 2nd place on Most Adopted Technology after @vite_js ⚡️💚
15
1,538
⚡️ Are you exploring the fediverse? Follow @vitest_dev in its new Mastodon home: @vitest@webtoo.ls 💚
webtoo.ls/@vitest
1
12
This is still a beta version. If you stopped using the previous extension or never used it, please try the new version and give us feedback! 💚
1
12
2,856
These versions also include patches for a browser mode security vulnerability.
github.com/vitest-dev/vitest…
1
5
2,400
@sheremet_va's talk about @vitest_dev is live!
Watch it at viteconf.org/live 💚⚡️
viteconf.org/tickets/shereme…
1
8
You can use "onTestFinished": vitest.dev/api/#ontestfinish…
6
458
„so much“ is a bit of stretch. When comparing 1 second to 2 seconds, it appears to be 2 times slower! But speed is not directly proportional to the number of tests (x2 times test will not lead to x2 worse performance)
2
1
7
3,276
Great article! One correction - Vitest has support for multi-project configuration via the workspace feature (vitest.dev/guide/workspace)
The next version also allows inline projects without the need to create a separate file!
1
3
39
Vitest provides vmForks pool which provides comparable speed to Jest setups: vitest.dev/config/#vmforks
1
3
60
We are planning to have a separate page about possible performance improvements developers can make with Vitest
2
3
81
Mocha is still faster in my tests (1.64s against 2.38s), though. There is more room to improve. I will investigate more during the week
1
2
123
As a rule, Vitest should be as fast as mocha with `singleThreads` flag, if it's not - it's a bug in Vitest
1
2
26
No, you can use it in any project. Using Vite as the engine make it able to reuse the plugins from your app, but it's not a requirement.
2
This is interesting! I would love to see a reproduction. My first point was the initialization of Vitest on the Node.js side (so, before we even fire up a worker to run tests), tests themselves import as little as possible to set up the runner itself
2
1
115
For me, disabling isolation made it 3 times faster using your reproduction. Maybe you had a typo?
3
1
84
My first instinct would be that the performance hit in the video might be because either:
> reporter performance (we had problems with it, but they should've been fixed)
> RPC performance (too much talking between thread and the main process)
1
87