Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork2.8k
Closed
Labels
Description
Suggestion
Right now, we useJest in this repository for unit tests. It works well. But, I've noticed unit tests starting to take quite a while. It'd be nice if we could reduce that speed.
Vitest purports to be much faster than Jest (and in my personal experience, is). If someone could send a draft PR with our repo migrated over to Vitest and all tests passing, it'd be nice to see:
- What would the actual code changes look like?
- How much faster would Vitest be?
Bonus points if someone can find or write codemods to do the migration automatically...!
Edit (April 2025): The initial normalization PRs are done and we're now merging the conversions for individual packages. This is roughly the order we're planning on as suggested by@aryaemami59 &@43081j:
- chore(eslint-plugin-internal): migrate from
jest
tovitest
#10771 - chore(typescript-eslint): migrate from
jest
tovitest
#10772 - chore(visitor-keys): migrate from
jest
tovitest
#10773 - chore(parser): migrate from
jest
tovitest
#10775 - chore(utils): migrate from
jest
tovitest
#10777 - chore(type-utils): migrate from
jest
tovitest
#10767 - chore: migrate
integration-tests
fromjest
tovitest
#10778 - chore(rule-tester): migrate from
jest
tovitest
#10779 - chore(scope-manager): migrate from
jest
tovitest
#10677 - chore(typescript-estree): migrate from
jest
tovitest
#10679 - chore(eslint-plugin): migrate to vitest #10579 &chore(eslint-plugin): migrate from
jest
tovitest
#10764 - chore(ast-spec): migrate from
jest
tovitest
#10770 - chore: migrate
rule-schema-to-typescript-types
fromjest
tovitest
#10774 - chore(types): migrate from
jest
tovitest
#10776