chore: use vitest for type testing

[KaiSpencer]

closes #2019

[KaiSpencer]

Hey @kettanaito,

I have made a first stab at this. Would it be possible for you to approve the workflow run so I can see if what I have done for the vitest config RE typescript versions is even remotely correct :D

[kettanaito]

@KaiSpencer, looks like some of your changes were reflected in the pnpm-lock.yaml. Could you please run pnpm install and commit the changes to the lockfile? That should unblock the CI. Thanks.

[KaiSpencer]

@KaiSpencer, looks like some of your changes were reflected in the pnpm-lock.yaml. Could you please run pnpm install and commit the changes to the lockfile? That should unblock the CI. Thanks.

I have done this and committed the lockfile, so should be good to go again on CI now

[KaiSpencer]

Hey @kettanaito I am happy with the type testing now. but there are some browser tests failing msw-api/setup-worker/life-cycle-events/on.test.ts

It seems the response.url is returning back as an empty string. Not quite sure why :D Any ideas?

[kettanaito]

@KaiSpencer, that's an unrelated issue (I think #2031).

[kettanaito]

You, sir, are incredible. Thank you for making this happen and welcome to contributors, @KaiSpencer 👏

[KaiSpencer]

You, sir, are incredible. Thank you for making this happen and welcome to contributors, @KaiSpencer 👏

Thank you for the support throughout this, It was a nice Issue/PR to get my foot in the door 🙇‍♂️

[kettanaito]

If you see any other tasks that interest you, don't hesitate to leave a comment!

[KaiSpencer]

I'll take a look 👀

[kettanaito]

Released: v2.2.10 🎉

This has been released in v2.2.10!

• 📄 Release notes
• 📦 npm package

Make sure to always update to the latest version (npm i msw@latest) to get the newest features and bug fixes.

---

Predictable release automation by @ossjs/release.