-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch to vitest #176
Switch to vitest #176
Conversation
This replaces Jest as a test runner with Vitest. Jest has too many issues resolving modules and running TypeScript. The tests were renamed to match Vitest’s default test pattern. The ESLint configuration was adjusted a bit to match the new setup as well.
Oh no, apparently Vitest requires Node.js 18 or greater, but this project supports Node.js 14. Do we want to test against older Node.js versions? I would prefer to even use |
Vitest doesn’t work in Node.js 16. Node.js 22 was added to the test matrix.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm as long as you tested locally (live-api) and see that the number of tests are the same as before, and coverage still works
This replaces Jest as a test runner with Vitest. Jest has too many issues resolving modules and running TypeScript.
The tests were renamed to match Vitest’s default test pattern.
The ESLint configuration was adjusted a bit to match the new setup as well.