Module resolution fails when using both haste and moduleNameMapper config options

[dcalhoun]

🐛 Bug Report

Utilizing both haste and moduleNameMapper config options causes Jest's module resolution to fail.

To Reproduce

1. Clone the test case repository.
2. yarn install
3. yarn test

Expected behavior

The required module resolves and the test passes.

Link to repl or repo (highly encouraged)

https://github.com/HealthTeacher/jest-haste-module-name-mapper

Run npx envinfo --preset jest

Paste the results here:

System:
  OS: macOS 10.14
  CPU: x64 Intel(R) Core(TM) i7-4750HQ CPU @ 2.00GHz
Binaries:
  Node: 10.8.0 - ~/.asdf/shims/node
  Yarn: 1.10.1 - /usr/local/bin/yarn
  npm: 6.2.0 - ~/.asdf/shims/npm
npmPackages:
  jest: ^23.6.0 => 23.6.0

Notes

• Replacing the root directory alias require with a relative require fixes the related test: const Greeter = require('./components/Greeter');
• Relocating components/Greeter/index.web.js to components/Greeter/index.js also fixes the related test.
• The combination of haste and moduleNameMapper config appears to cause an issue.

Error Output

FAIL  __tests__/index.test.js
 ● Test suite failed to run

   Configuration error:

   Could not locate module ~/components/Greeter mapped as:
   /Users/username/Sites/oss/jest-haste-module-name-mapper/components/Greeter.

   Please check your configuration for these entries:
   {
     "moduleNameMapper": {
       "/^~\/(.*)/": "/Users/username/Sites/oss/jest-haste-module-name-mapper/$1"
     },
     "resolver": null
   }

   > 1 | const Greeter = require('~/components/Greeter');
       |                         ^
     2 |
     3 | // Replacing the above `require` with below fixes the related test
     4 | // const Greeter = require('./components/Greeter');

     at createNoMappedModuleFoundError (node_modules/jest-resolve/build/index.js:411:17)
     at Object.<anonymous> (index.js:1:25)

[grosto]

I can try to tackle this one if help is still needed

[dcalhoun]

@grosto still an active bug from what I know. Thank you!

[grosto]

@dcalhoun it seems to be fixed with this PR #7312.

[dcalhoun]

@grosto looks like you may be correct. I can't re-test my original reproduction example right now, but I'll try to do so later.

[rickhanlonii]

Going to optimistically close, if it's still an issue let us know and we'll re-open 👍

[github-actions]

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.