-
Notifications
You must be signed in to change notification settings - Fork 47.2k
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
Downgrade Jest to 24 #18376
Downgrade Jest to 24 #18376
Conversation
Not sure it's going to be that easy due to jsdom changes. The upgrade was rather involved: #17896. |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit a622dad:
|
Wonderful. |
@SimenB Do you mind doing a patch release for jestjs/jest#9575? |
This reverts commit cf00812. The changes to the test code relate to changes in JSDOM that come with Jest 25: * Several JSDOM workarounds are no longer needed. * Several tests made assertions to match incorrect JSDOM behavior (e.g. setAttribute calls) that JSDOM has now patched to match browsers. * https://codesandbox.io/s/resets-value-of-datetime-input-to-fix-bugs-in-ios-safari-1ppwh * JSDOM no longer triggers default actions when dispatching click events. * https://codesandbox.io/s/beautiful-cdn-ugn8f * JSDOM fixed (jsdom/jsdom#2700) a bug so that calling focus() on an already focused element does not dispatch a FocusEvent. * JSDOM now supports passive events. * JSDOM has improved support for custom CSS properties. * But requires jsdom/cssstyle#112 to land to support webkit prefixed properties.
Fortunately cf00812 reverts pretty cleanly. I thought it was a big diff but it's mostly only yarn.lock changes. |
Did you test if the bugfix actually fixes all the things? The fix doesn't seem fully correct to me. E.g. what happens if we implement a setter that throws instead of freezing. Which we do sometimes. |
It fixes comparing JSX. I tested with |
Oh you mean the fix in master, not the revert. I didn't test that, no. |
Comparing SyntheticEvent might fail.
|
I don't have publish access, only FB employees do. You can try to ping @scotthovestadt or @DiZy internally? Or @cpojer might be able to |
Sorry for inconvenience @SimenB, I just followed up with our team and you should have access to all packages now. |
Cool, thanks! I've published 25.2.0 now.
This probably isn't fixed though, maybe open up an issue with a test that fails which should pass? |
Current blocker: jestjs/jest#9745 |
25.2.7 published with fix for ^. Thanks for the help landing it @gaearon! |
This reverts commit fc7835c.
There's a bug where
toEqual
throws when comparing readonly properties, which affects our JSX matchers.jestjs/jest#9575
The bug is fixed in master, but not yet released.
Until then, downgrading to 24.