Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork2.8k
test(eslint-plugin): improve vitest performance#11754
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
test(eslint-plugin): improve vitest performance#11754
Conversation
Thanks for the PR,@StyleShit! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently onhttps://opencollective.com/typescript-eslint. |
netlifybot commentedNov 11, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
✅ Deploy Preview fortypescript-eslint ready!
To edit notification comments on pull requests, go to yourNetlify project configuration. |
nx-cloudbot commentedNov 11, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
View yourCI Pipeline Execution ↗ for commitba9a193
☁️Nx Cloud last updated this comment at |
StyleShit commentedNov 11, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Update: After comparing it to 3 random runs (1,2,3), seems like it's indeed faster (3m 26s vs 5m 10s / 5m 1s / 4m 59s) Not sure why itfails in Node 20 though... Seems like it's flaky for some reason. Maybe there are non-pure tests after all. will investigate when I have some time |

Uh oh!
There was an error while loading.Please reload this page.
Trying to help a little bit with#11204
Since all (most?) eslint-plugin tests are free of side-effects, I wondered whether we can improve the performance bydisabling isolation
On my local machine (M4 Pro, 24GB, Node v22.21.1), I saw an improvement of ~18% in an average of 3 runs.
If this works, we might be able to do this with other packages that have "pure" tests