Closed
Description
Before You File a Bug Report Please Confirm You Have Done The Following...
- I have tried restarting my IDE and the issue persists.
- I have updated to the latest version of the packages.
- I have searched for related issues and found none that matched my issue.
- I have read the FAQ and my problem is not listed.
Issue Description
Switching from parserOptions.project: true
to parserOptions.EXPERIMENTAL_useProjectService
should in the worst case scenario should be roughly the same speed as before. The best case scenario should be faster. But checking it out on the getsentry/sentry project, I'm seeing a raise from ~50s/65s to ~80s/110s. 😬
Baseline:
$ time yarn lint:js
yarn run v1.22.19
$ eslint static/app tests/js --ext .js,.jsx,.ts,.tsx
✨ Done in 49.47s.
yarn lint:js 65.43s user 3.26s system 138% cpu 49.607 total
With the project service:
$ time yarn lint:js
yarn run v1.22.19
$ eslint static/app tests/js --ext .js,.jsx,.ts,.tsx
✨ Done in 81.42s.
yarn lint:js 108.11s user 8.10s system 142% cpu 1:21.55 total
Thanks @yagiz for reporting!
Reproduction Repository Link
Repro Steps
- Clone
getsentry/sentry
time yarn lint:js
- Enable
parserOptions.EXPERIMENTAL_useProjectService
time yarn lint:js
Versions
package | version |
---|---|
@typescript-eslint/eslint-plugin |
6.19.0 |
@typescript-eslint/parser |
6.19.0 |
TypeScript |
5.3.2 |
ESLint |
8.49.0 |
node |
20 |
Metadata
Metadata
Assignees
Labels
Something isn't workingSomething isn't workingPlease open a new issue if you'd like to say more. See https://typescript-eslint.io/contributing.Please open a new issue if you'd like to say more. See https://typescript-eslint.io/contributing.Issues regarding performanceIssues regarding performanceA member of the typescript-eslint team should work on this.A member of the typescript-eslint team should work on this.