#Vitest

Doug Parker 🕸️'s avatar
Doug Parker 🕸️

@develwithoutacause@techhub.social

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 demo (ironically one showing that it doesn't solve this particular use case).
2. My auto setup using and failed to parse `@layer`.
3. I upgraded .
4. I removed and replaced it with , which works with `@layer`.
5. I wanted to use `Object.groupBy` here which requires `target: "ES2024"` in .
6. Therefore I needed to upgrade TS.
7. Upgrading TS broke for reasons I couldn't understand.
8. Therefore I migrated from Karma to (which I've wanted to do anyways).
9. Now 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.

answers.netlify.com/t/netlify-

洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@hongminhee@hollo.social

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

洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@hongminhee@hollo.social

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

洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@hongminhee@hollo.social

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