Support absolute path to custom extension through haste package #3537
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
This PR adds support for absolute resolution of files with custom extension in haste packages.
Jest support so-called "haste packages" which allow to place
package.json
with aname
property providing a custom namespace for modules inside directory it resides. Since resolution for these haste packages userequire.resolve
, it doesn't support absolutely resolving custom extensions, like.ios.js
or.android.js
, it's just working with.js
files.Such resolution mechanism works in React Native, I think it would be nice for Jest to support it.
Fixes #3342.
Test plan
Integration test.