#Vitest

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

#testing #javascript #vitest #vite

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

#testing #javascript #vitest #vite

Over the last few days while working on an upcoming blog post I've performed quite the yak shaving:

1. I wanted to use `@layer` in a #CSS demo (ironically one showing that it doesn't solve this particular use case).
2. My auto #CSP setup using #JSDom and #CleanCSS failed to parse `@layer`.
3. I upgraded #CleanCSS.
4. I removed #JSDom and replaced it with #parse5, which works with `@layer`.
5. I wanted to use `Object.groupBy` here which requires `target: "ES2024"` in #TypeScript.
6. Therefore I needed to upgrade TS.
7. Upgrading TS broke #Karma for reasons I couldn't understand.
8. Therefore I migrated from Karma to #Vitest (which I've wanted to do anyways).
9. Now #Netlify is confused that I have both an 11ty and Vite project and fails, asking me to pick one.
10. I pick one in `netlify.toml`, but a bug in Netlify refuses to accept it.

https://answers.netlify.com/t/netlify-ignores-framework-configuration-and-throws-error-detected-commands-for-eleventy-vite/156020

Anyone here have experience using @vitest with @deno_land, or setting up a unit test suite that works on #Deno, #Node.js, and #Bun?

#Vitest #JavaScript #TypeScript

Anyone here have experience using @vitest with @deno_land, or setting up a unit test suite that works on #Deno, #Node.js, and #Bun?

#Vitest #JavaScript #TypeScript

Anyone here have experience using @vitest with @deno_land, or setting up a unit test suite that works on #Deno, #Node.js, and #Bun?

#Vitest #JavaScript #TypeScript