Project is at github.com/AriPerkkio/a...

Same tests run in browser and JSDOM:

Does not work on Mac with latest Bun:

Setting custom `process.title` in Node takes around 10-20ms. Vitest used to do this for every isolated test file so that debugging test runner processes was a bit nicer experience. But it's not worth the performance hit.

test-exclude usage is removed in Vitest v4. 0 new deps were needed, as `vitest` package already had all required replacements.
github.com/vitest-dev/v...

We've added new coverage provider comparison page on Vitest documentation. This guide describes the lower level differences between Istanbul and V8. It should help users choosing which provider to use. vitest.dev/guide/covera...

Onboarding on new @storybook.js.org projects is just perfect. So nice to have testing setup *covered* out-of-the-box. 🤝

Tinypool is now built with tsdown! Migration from tsup was smooth and required minimal changes. Thanks to @sxzz.dev 💯

After couple of days looking at *.cpuprofile's, I think it's getting closer to stable v1 release. The ~3MB checker.ts from Typescript repo is perfect benchmarking reference for tools that process source code. When generating coverage for 'vuejs/core' repo, speed is close to original v8-to-istanbul.

This release includes long-awaited "--silent=passed-only" option, that can be used to hide console.log calls from passing tests. Only the logs from failing tests are reported.

Finalizing rewrite of AST-aware v8-to-istanbul. This will provide accuracy of Istanbul coverage for V8 coverage reports. I've intentionally kept this tool unopinionated so that it's not strictly tied to just @vitest.dev - it should be usable with Jest, C8, Playwright and node:test too.

Tree-view of @vitest.dev verbose reporter is coming back! We (well I did) forgot to implement this during v3's reporter rewrites. I had already forgot how good it looks.

🫠

This kind of growth just amazes me. On 12/2023 Vitest had 3M weekly downloads. Now in 12/2024 there's almost 8M. Maybe we can share #2 with Storybook next year! 📈
2024.stateofjs.com/en-US/librar...

Give it a try instead! Here I have ~160 tests running faster in browser mode than in JSDOM, ~320ms vs ~500ms. I'm testing my utility library against real browsers and JSOM with Vitest's workspaces.

Today I was testing a fix for a bug that required to have the dependent project deployed on real infra. Testing this without pkg.pr.new would have required so much extra work. 🤝

Released in 2.2.0-beta.2 and it's even smoother now! Here's comparison of latest Vitest on left vs beta on right. Flickering is gone and now you can scroll up to see results without scroll jumping. And of course there's the status summary of active test run on the bottom. github.com/vitest-dev/v...

Contents of lesson can be downloaded with a single click:

TutorialKit v1.3.0 is now out! 🥳
You can now omit part and chapter levels if your tutorial doesn't need that deeply nested architecture! There is also new 'downloadAsZip' option that adds button for downloading whole lesson as .zip-file with a single click.
Release notes: github.com/stackblitz/t....

Hello 🦋! Here's sneak peek into Vitest reporter improvements I've been working on for a while now. This reduces terminal flickering, fixes scroll issues and adds status summary. It's still WIP but looking really good so far!