-
-
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
support for node version 10.13.0 #10658
Comments
I'm having the same problem. When I check the master of @jest/types, the engines specification is as follows. I've also seen that the engines designation has been changed in the PR here. 54955a4#diff-bda31c99aca44f95480bae4c77c02a63b6a99da3f15c570aea9a3f7d0280b60e Does that mean that a version with the changed engines designation will be released soon? |
Changed in #10685, will be released in Jest 27. Hopefully released this side of Christmas, but no promises. https://github.com/facebook/jest/milestone/12 We will not be releasing any new versions of Jest 26 |
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. |
💬 Questions and Help
I am using the latest version of react testing library https://testing-library.com/docs/intro which is 11.1.0
But can not run the CI/CD pipeline with a docker image which has a node version 10.13.0.
I have filed an issue in the react testing library:
testing-library/react-testing-library#804
They refer to the following link:
https://unpkg.com/@jest/types@26.6.0/package.json
saying that the issue comes from jest/types which has support only for engines with "node": ">= 10.14.2"
Question: Is there any upcoming release foreseen where the engine's node could be downgraded to >= 10.13.0 ? Or any suggestions, cause it doesn't matter if I install jest with lower version the react testing library always has a peerDependency to newer jest/types@26.6.0?
Please note that this issue tracker is not a help forum and this issue will be closed.
For questions or help please see:
#testing
channel in ReactifluxThe text was updated successfully, but these errors were encountered: