skipNodeResolution config option

[aaronabramov]

this option was used internally at fb but was dead code in oss version.
I'm not sure what exactly it does, but without it it takes Jest more than 2 minutes to find reverse dependencies of changed files.

i don't know if it's useful for the OSS world at all. If yes, we should document it, if not we should probably add some experimental flag or something

[codecov-io]

Codecov Report

❗ No coverage uploaded for pull request base (master@6ae7b02). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #3987   +/-   ##
=========================================
  Coverage          ?   60.28%           
=========================================
  Files             ?      196           
  Lines             ?     6768           
  Branches          ?        6           
=========================================
  Hits              ?     4080           
  Misses            ?     2685           
  Partials          ?        3

Impacted Files	Coverage Δ
packages/jest-config/src/index.js	0% <ø> (ø)
packages/jest-resolve/src/index.js	14.01% <ø> (ø)
packages/jest-cli/src/search_source.js	76.27% <ø> (ø)
packages/jest-config/src/valid_config.js	100% <ø> (ø)
packages/jest-haste-map/src/index.js	92.96% <ø> (ø)
packages/jest-config/src/normalize.js	84.66% <ø> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6ae7b02...16d88fd. Read the comment docs.

[cpojer]

Yap, this only makes sense in an environment where haste is the primary module resolution system.

[github-actions]

This pull request 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.