-
Notifications
You must be signed in to change notification settings - Fork 455
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
feat: support jest 27 #2171
feat: support jest 27 #2171
Conversation
Yes there are a few breaking changes for transformer requiring some changes in |
The version checking should be changed too ts-jest/src/utils/version-checkers.ts Line 13 in 6de7509
If you correct all the comments above + adjust tests, I think that should be enough |
5930de8
to
040652c
Compare
Pull Request Test Coverage Report for Build 409095633
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
global.gc
is not exposed. jest-jasmine
doesn't report correctly error while jest-circus
does, see more information here jestjs/jest#9882
it(`should report correct line numbers`, () => { | ||
// TODO: Refactor e2e tests to have more stable tests. | ||
// eslint-disable-next-line jest/no-disabled-tests | ||
it.skip(`should report correct line numbers`, () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this test is flaky. We need to improve e2e tests setup.
@kulshekhar I think we are good in compatibility with jest 27 for this PR. |
9546334
to
1002708
Compare
BREAKING CHANGE Require minimum jest 27
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary
Adopt changes to work with jest 27
Set required jest to
27.0.0-next.2
. Later when jest releases27.0.0
, we need to update required version to be27.0.0
. For now we can temporarily publish with current required version fornext
tagDoes this PR introduce a breaking change?
Ohhhhh yeah.