Stops calling existsSync on object configs #7607
Merged
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
The previous code was calling
existsSync
by passing aroot
to it, which could either be a string or a Jest configuration object. TheexistsSync
implementation currently accepts both, but this behavior is frowned upon and might be deprecated in later Node releases. This diff simply checks whether the root is a path before callingexistsSync
on it.cc @rubennorte
Test plan
Not easy to test since it currently works even without the PR 😄