[jest-resolve] Add support for packageFilter
for custom resolvers
#10393
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
Forwards option
packageFilter
toresolve
. This is useful in case a custom resolver wants to use it. The best example is #2702 (in particular, #2702 (comment))Fixes #2702
Test plan
Write a custom resolver like
Then, in any jest test, when importing package
X
, it will try to load it from the fieldmodule
first, with fallback tomain
ifmodule
doesn't exist.