🚀 Feature Proposal
If user updated minor version of jest to 30.4 (I know this happens if previous version was 30.2) and forgets to update jest-environment-jsdom to version 30, then he gets a bit cryptic error message:
Test suite failed to run
TypeError: this._moduleMocker.clearMocksOnScope is not a function
at Runtime.resetModules (../jest/packages/jest-runtime/build/index.js:3781:28)
It would be nice if user instead got error message, that would help him fix the issue (in a sense of "update your jsdom").
Motivation
Without proper error message, people might get lost and spend a lot of time trying to figure out what went wrong.
Example
Running the test with old version should produce an error of "update your jest-environment-jsdom to latest version"
Pitch
Because it's about interoperability between jest and it's component
🚀 Feature Proposal
If user updated minor version of jest to 30.4 (I know this happens if previous version was 30.2) and forgets to update jest-environment-jsdom to version 30, then he gets a bit cryptic error message:
Test suite failed to run
TypeError: this._moduleMocker.clearMocksOnScope is not a function
at Runtime.resetModules (../jest/packages/jest-runtime/build/index.js:3781:28)
It would be nice if user instead got error message, that would help him fix the issue (in a sense of "update your jsdom").
Motivation
Without proper error message, people might get lost and spend a lot of time trying to figure out what went wrong.
Example
Running the test with old version should produce an error of "update your jest-environment-jsdom to latest version"
Pitch
Because it's about interoperability between jest and it's component