-
Notifications
You must be signed in to change notification settings - Fork 459
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
Add support for Jest 27 #2611
Comments
Thanks for notification, we already prepare for it at next tag so we will prepare for latest tag soon. |
@ahnpnl Can you give some indication of when soon is? Also, it would be helpful to keep this issue open while the problem exists, I had assumed it was resolved given you'd closed it. |
it is resolved in |
Ideal, thank you. |
@ahnpnl, looks like npm still points |
|
27.0.0 was out |
Please clear Jest cache. Also check your lock file to make sure You can also remove |
Thanks @ahnpnl for your (I must say) incredibly fast response. I have:
Unfortunately, error keeps there :( I can provide a repo if needed Edit: Testing repo here |
You are using Jest 26 with |
thanks a lot @ahnpnl . As you said, this was the issue. Seems that CRA installs jest 26! Thanks a lot EDIT: for whoever reaching this post, if you are using react-scripts 4.0.3 or below, it internally uses jest 26, so installing ts-jest 27 will crash everything. You can force react-scripts to use jest 27 using yarn |
I am still facing the issue while upgrading
Using
|
I'm having the same problem as @suvasishm |
1 similar comment
I'm having the same problem as @suvasishm |
Hey everyone! I'd appreciate your help! |
I managed to solve it. Just run the |
🐛 Bug Report
Upgrading to Jest 27 leads to the following error:
TypeError: Jest: a transform must export something.
Also the peer dependency scope should be updated alongside this fix:
warning " > [email protected]" has incorrect peer dependency "jest@>=26 <27".
To Reproduce
Upgrade from Jest 26 to Jest 27.
Expected behavior
Running the
jest
command to successfully run tests.Debug log:
envinfo
The text was updated successfully, but these errors were encountered: