Previously using Jest as a test suite it was noticed that there were a number of issues requiring different packages to accomplish testing. There were too many hoops to jump through in order to get it working on Vite.
Description
In order to accomplish this, I decided to move to Vitest and in order to get some of the modern goodness of this suite I decided to update Vite from 4.x to 5.x with a few other packages to updated as a requirement.
Something note worthy to mention is that Vitest runs incredibly fast compared to Jest in this case.
Contribution Checklist
[x] I have built and tested the code locally and in a deployed app
[x] For frontend changes, I have pulled the latest code from main, built the frontend, and committed all static files.
[x] This is a change for all users of this app. No code or asset is specific to my use case or my organization.
[x] I didn't break any existing functionality :smile:
Motivation and Context
Previously using Jest as a test suite it was noticed that there were a number of issues requiring different packages to accomplish testing. There were too many hoops to jump through in order to get it working on Vite.
Description
In order to accomplish this, I decided to move to Vitest and in order to get some of the modern goodness of this suite I decided to update Vite from 4.x to 5.x with a few other packages to updated as a requirement.
Something note worthy to mention is that Vitest runs incredibly fast compared to Jest in this case.
Contribution Checklist