Performance of back-to-back ts-eslint runs #9046
Closed
innermatrix
started this conversation in
Technical Discussions
Replies: 1 comment
-
As per our discussion guidelines we don't use discussions for support. Consider using discord or similar. The guidelines contain helpful suggestions and links. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Body
I find myself in a situation where I want to run
eslint
twice back-to-back in circumstances where the source will typically remain unchanged between two runs (think: pre-commit hook or CI pipeline). I use type-aware rules, and I know that due to the current architecture ofeslint
andts-eslint
I need to pay the penalty of constructing all type information before a single file can be linted.However…
Is there a way that I can avoid paying the penalty twice when making two back-to-back
eslint
runs (if the source is unchanged)? As I understand it, theeslint --cache
option is unhelpful here because the presence of type-aware rules busts theeslint
cache.(The use case here is that I would like to use
eslint
for checking rules that have been adopted by my team, andbetterer
for checking rules that are being incrementally adopted, andbetterer
is challenging to configure as a runner for alleslint
rules due to its own architectural decisions.)Additional Info
Any additional info...
Before you submit your discussion, please confirm the following. If any of these required steps are not taken, we may not be able to review your RFC. Help us to help you!
Beta Was this translation helpful? Give feedback.
All reactions