Disabling automock breaks detection of file extension when using moduleNameMapper

[codeheroics]

Hi,

I'm trying to setup with jest 13.2.3 on my current project. We use the webpack alias feature to get simpler module paths (eg. import en from 'i18n/en'; instead of import en from '../../../../i18n/en'), so I've followed this tutorial to setup the package.json for jest, using moduleNameMapper to setup this kind of rule:

{
    "moduleNameMapper": {
      "^i18n": "<rootDir>/src/i18n"
    }
}

Which worked correctly in my test file:

import en from 'i18n/en';
console.log(en); // logs the exported contents of en.js

However, when I tried to disable automock, either via setting automock: true in the package.json or using jest.disableAutomock(), I run into this file not found error:
Error: ENOENT: no such file or directory, stat '/home/codeheroics/dev/front/src/i18n/en'

Am I misunderstanding something in my moduleNameMapper setup, or is there a need to activate automock to get correct file extension detection when using it ?
(I'm overwriting moduleFileExtensions to handle .jsx files, but this problem exists with .js files whether or not it is overwritten)

[cpojer]

As a workaround, can you use moduleDirectories instead?

[codeheroics]

Using moduleDirectories works perfectly as a workaround, thanks!

[cpojer]

Ok, I think that's the right solution here actually.

[codeheroics]

Isn't it weird that setting or not automock changes the file loading abilities? (and it still feels problematic as moduleNameMapper is the recommended way, in tutorial, to handle webpack aliases, so others could run in the issue)

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