Suggestion

Right now, we use Jest 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 to vitest #10771
• chore(typescript-eslint): migrate from jest to vitest #10772
• chore(visitor-keys): migrate from jest to vitest #10773
• chore(parser): migrate from jest to vitest #10775
• chore(utils): migrate from jest to vitest #10777
• chore(type-utils): migrate from jest to vitest #10767
• chore: migrate integration-tests from jest to vitest #10778
• chore(rule-tester): migrate from jest to vitest #10779
• chore(scope-manager): migrate from jest to vitest #10677
• chore(typescript-estree): migrate from jest to vitest #10679
• chore(eslint-plugin): migrate to vitest #10579 & chore(eslint-plugin): migrate from jest to vitest #10764
• chore(ast-spec): migrate from jest to vitest #10770
• chore: migrate rule-schema-to-typescript-types from jest to vitest #10774
• chore(types): migrate from jest to vitest #10776