Tree shanking for re-exported entry

[yola-0316]

🚀 Feature Proposal

As the following description. In watch mode, Container A related test suits will not run while Button Change:

As a developer, I only want to rerun related tests.

Now:

• jest collectModules logic not expose to user.
• jest dependencyExtractor use regex match.

Hope:

• dependencyExtractor extract dependencies with import export info.
• collectModules let use decided which file need to run.

Motivation

My project use index.tsx re-exported a lot of components.
In jest watch mode, many relationship test suites run when I change only one basic component.

If could tree shaking the re-exported entry, would reduce many times.

Example

According to above picture, When Button changed, Container A related test will not running.
Only Tab component changed, Container A will run.

Pitch

Why does this feature belong in the Jest core platform?

Common feature proposals that do not typically make it to core:

• New matchers (see jest-extended)
• Changes to the default reporter (use custom reporters instead)
• Changes to node/jsdom test environments (use custom environments instead)

[ahnpnl]

#11234 talks about similar thing (entry/barrel) but more about performance in that 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.