Closed
Description
🚀 Feature Proposal
Can jest support tree-shaking to prevent mistakes that could have been avoided in jest.
Motivation
There is two function exported from XXX package.
export { default as A } from './A'
export { default as B } from './B'I only use A function fron XXX package. Howerver, It has an error on B function in Jest.
It's sad I'm not expect it has an error on B function because I don't use it.
Example
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)