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 Stepsgetsentry/sentry
time yarn lint:js
parserOptions.EXPERIMENTAL_useProjectService
time yarn lint:js
@typescript-eslint/eslint-plugin
6.19.0
@typescript-eslint/parser
6.19.0
TypeScript
5.3.2
ESLint
8.49.0
node
20
You can’t perform that action at this time.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4