[Bug]: require.resolve.paths cannot reach global path in the scope of jest

Version

v29.1.2, the newest

Steps to reproduce

Minimal reproduction: https://github.com/lvqq/jest-require-resolve-paths

Steps:

1. npm install
2. npm test

Expected behavior

require.resolve.paths is consistent in jest and in node

Actual behavior

In node, require.resolve.paths(‘npm’) returns:

[
  'D:\\RD\\project\\jest-require-resolve-paths\\node_modules',
  'D:\\RD\\project\\node_modules',
  'D:\\RD\\node_modules',
  'D:\\node_modules',
  'C:\\Users\\chlorine\\.node_modules',
  'C:\\Users\\chlorine\\.node_libraries',
  'D:\\RD\\nodejs\\lib\\node'
]

In the scope of jest, require.resolve.paths(‘npm’) returns:

[
  'D:\\RD\\project\\jest-require-resolve-paths\\node_modules',
  'D:\\RD\\project\\node_modules',
  'D:\\RD\\node_modules',
  'D:\\node_modules'
]

The global paths are missing.

Additional context

No response

Environment

System:
    OS: Windows 10 10.0.19044
    CPU: (16) x64 Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz
  Binaries:
    Node: 16.17.0 - D:\RD\nodejs\node.EXE
    Yarn: 1.22.10 - D:\RD\nodejs\node_global\node_modules\yarn\bin\yarn.CMD    npm: 8.15.0 - D:\RD\nodejs\npm.CMD
  npmPackages:
    jest: ^29.1.2 => 29.1.2

[jeysal]

Cool! In case this helps your get started: require and require.resolve and require.resolve.paths are implemented by jest-runtime, which then does some calls to jest-resolve which knows things like how to look up in the directory tree to look for node_modules etc.

[lvqq]

Thanks! I’d like to work on implementing it