fix(config): invalidate cache when other options in tsconfig change #1788
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.
Summary
At the moment, only
compilerOptions
intsconfig.json
is considered in cache key. However, if users change other options likeinclude
orexclude
, the cache isn't invalidated. Sinceinclude/exclude
impacts on performance withts-jest
, it makes sense to include them into cache key.This PR is to invalidate cache whenever other options (
include/exclude/projectReferences
) fromtsconfig.json
changeTest plan
Green CI
Does this PR introduce a breaking change?
Other information
N.A.