Upgrade dependencies, migrate to vitest #303
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We were on a quite old version of typescript, jest, etc. so I've tried to upgrade them.
However, I've found a lot of issues trying to get jest to work. Apparently their support for ESModules is still "experimental" and it's a nightmare to set up (specially with typescript in-between).
After trying for an hour I've decided to migrate it to vitest, which is way more out-of-the-box, specially with typescript support.
The only "drawback" is that we need to import the describe/it functions. In theory we don't actually need it because I've set up
globals: true
, because react-testing-library needs that, but I don't know how to tell typescript that these globals are available only on test files. So anyway, I think it doesn't hurt that much.Accidentally closes #290 and #294