Jest-resolve broken: getMockModule throws an error

[FrontendMMA]

💥 Regression Report

A clear and concise description of what the regression is.

Last working version

Worked up to version: 26.6.1

Stopped working in version: 26.6.2

To Reproduce

Steps to reproduce the behavior:

jest.config.js

'moduleNameMapper': {
    '^ui(.*)': '<rootDir>/ui$1',
}

import xSelector from "selectors/ui.selector.js"

throw error

Configuration error:

Could not locate module ui.selector mapped as:
/Users/xxx/Projects/xxx/src/ui$1.

Please check your configuration for these entries:
{
  "moduleNameMapper": {
    "/^ui(.*)/": "/Users/xxx/Projects/xxx/src/ui$1"
  },
  "resolver": undefined
}

Expected behavior

not throwed

Link to repl or repo (highly encouraged)

Run npx envinfo --preset jest

  System:
    OS: macOS 10.15.2
    CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
  Binaries:
    Node: 13.6.0 - ~/.nvm/versions/node/v13.6.0/bin/node
    Yarn: 1.21.1 - ~/.yarn/bin/yarn
    npm: 6.13.4 - ~/.nvm/versions/node/v13.6.0/bin/npm
  npmPackages:
    jest: 26.1.0 => 26.1.0 

I can fix the regex, but the problem persists for others

This error here https://github.com/facebook/jest/blob/master/packages/jest-resolve-dependencies/src/index.ts#L78

[SimenB]

From #10713 - @jeysal @brapifra ideas?

[SimenB]

Should we just try-catch the getMockModule call?

@FrontendMMA do you have a reproduction we can pull down and test?

[brapifra]

Sorry to see this regression! 😿

Should we just try-catch the getMockModule call? @SimenB
I think this should work. A reproduction would be certainly helpful.
Happy to open a PR if needed!

[FrontendMMA]

Sorry, I can't provide the project
checked: try/catch works

[SimenB]

Can you reduce it down? Just delete all code except the test file, the file it resolves to and the minimal jest config needed? A try/catch is not the correct solution I'd think - we shouldn't throw in the first place

[FrontendMMA]

https://github.com/FrontendMMA/jest-resolve--bug-example

1. change test file or tested file (App.js / App.test.js)
2. execute jest -o (repeats in a "onlyChanged" mode)

[SimenB]

Thanks @FrontendMMA! I had to change some stuff to make it work and understand where the regression was, I opened a PR: FrontendMMA/jest-resolve--bug-example#1

@brapifra would you be able to take a look at this? If you look at my branch it can be reproduced by removing the resolutions, running yarn and then follow the steps @FrontendMMA lists out in the comment above.

[brapifra]

Yes, I will look into this tomorrow @SimenB

[SimenB]

Thanks!

[SimenB]

Fix released in https://github.com/facebook/jest/releases/tag/v26.6.3

[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.