[Bug]: Custom resolver cannot intercept import fs

[ChocolateLoverRaj]

Version

27.5.1

Steps to reproduce

1. Clone my repo at https://github.com/ChocolateLoverRaj/jest-bug-2
2. Install dependencies
3. Run npm test
4. Look at output for fs and never logs

(never) Is to show that the resolver is getting npm packages, but not the fs module.

Expected behavior

I expect to see never and fs

Actual behavior

I see never, but not fs

Additional context

This bug is affecting the development of https://github.com/ChocolateLoverRaj/mock-deep. In that repo, I'm trying to actually mock files that could be ESM.

Environment

System:
    OS: Windows 10 10.0.19044
    CPU: (8) x64 Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
  Binaries:
    Node: 16.13.0 - C:\Program Files (x86)\Nodist\bin\node.EXE
    npm: 8.1.0 - C:\Program Files (x86)\Nodist\bin\npm.EXE
  npmPackages:
    jest: ^27.0.6 => 27.5.1

[SimenB]

Yeah, we don't call custom resolvers on node core modules: https://github.com/facebook/jest/blob/a5f1ef43981b7426d61bcd7cbc59a79f548c075a/packages/jest-resolve/src/resolver.ts#L221-L223 & https://github.com/facebook/jest/blob/a5f1ef43981b7426d61bcd7cbc59a79f548c075a/packages/jest-resolve/src/resolver.ts#L295-L297, added in #11817. I guess we should only skip calling the resolver if it's our own, and not custom resolvers. Wanna send a PR?

[ChocolateLoverRaj]

Wanna send a PR?

I will try

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