You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I spent a lot of time trying to figure out why my configuration for moduleNameMapper was not working. At the end of the day, the issue was simply that I had a mis-spelling in the path name. But, I'm curious as to why Jest did not report that as an error? It would have made my job so much easier if this had not been a "silent fail".
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.
I spent a lot of time trying to figure out why my configuration for
moduleNameMapper
was not working. At the end of the day, the issue was simply that I had a mis-spelling in the path name. But, I'm curious as to why Jest did not report that as an error? It would have made my job so much easier if this had not been a "silent fail".Here is what I did:
Result: Jest continued to run all tests, as normal. Nothing was different if I took this bit of code out. It was the same either way.
Ideal result:
A console error saying: "/some/incorrect/path.js does not exist. Please provide a correct path."
The text was updated successfully, but these errors were encountered: