Tighten up module mappers to prevent hard-to-debug bugs #53
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.
Fixes #41
Fixes #37
In #6 we introduced very loose
moduleNameMapper
which resulted in couple of weird bugs and until next Jest release it's impossible to override it.This PR reverts it and adds some reasonable defaults.
Also, because of this
"(.*)"
mapping, while debugging #41 on master version of Jest, I encountered an issue where one of the internal Jest modules was calling path matching the regexp, but couldn't find it undersrc
dir. This surfaced only because Jest version on master supports checking if modules inmoduleNameMapper
exist and throws otherwise.