Don't cache ESLint results #295
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The `eslint` executable takes a `--cache` option, which instructs ESLint to save the results of linting for each file, skipping linting in the future for files that haven't changed. While this does tend to make repeated runs faster, in other repos where this technique is also used, we've noticed that the cache can also give misleading output when running `eslint` with various other options, making debugging lint issues frustrating. It is better in the long run to disable caching.
Gudahtt
approved these changes
Dec 11, 2025
Member
Gudahtt
left a comment
Gudahtt
left a comment
There was a problem hiding this comment.
LGTM! Thanks I meant to do this but forgot
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
eslintexecutable takes a--cacheoption, which instructs ESLint to save the results of linting for each file, skipping linting in the future for files that haven't changed. While this does tend to make repeated runs faster, in other repos where this technique is also used, we've noticed that the cache can also give misleading output when runningeslintwith various other options, making debugging lint issues frustrating. It is better in the long run to disable caching.Examples
Note
Remove ESLint cache by changing
lint:eslintscript fromeslint . --cachetoeslint ..Written by Cursor Bugbot for commit aa92948. This will update automatically on new commits. Configure here.