-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature]: Option to support Error#cause
in snapshots for Jest29
#14916
Comments
We don't really do backporting. But even if we make it optional in Jest 30, I'm not 100% sure how it'd be configured 🤔 Might make more sense for you to create your own snapshotmatcher that ignores the |
You were able to work around it? |
Since Jest 30.0.0-alpha.2 works on Node.js v14 and snapshots |
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. |
🚀 Feature Proposal
Since we will drop support for Node.js v14. It's easier to just simply use Jest29 in node14.
But the snapshots won't match since Jest30 snapshots
Error#cause
, and it's hard to solve, suggest to backport #13965 but behind an option.Motivation
Driving me crazy... prettier/prettier#16106
Example
No response
Pitch
N/A
The text was updated successfully, but these errors were encountered: