-
Notifications
You must be signed in to change notification settings - Fork 2.7k
[MM-34187] - Update React version to 17* #10739
Conversation
E2E tests not automatically triggered, because PR has no approval yet. Please ask a developer to review and then try again to attach the QA label. |
@nevyangelova should we keep the QA review. Just in case to run e2e test and a smoke test of the app to see if stuff broke? |
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.
Looks good to me, I'll approve this to have the e2e tests run.
E2E tests not automatically triggered, because the PR is not in a mergeable state. Please update the branch with the base branch and resolve outstanding conflicts. |
@nevyangelova sadly, there's a conflicting package.json now. |
@hmhealey kind reminder to review :) |
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.
Could you also update react-is
and @hot-loader/react-dom
? If I understand correctly, those have to be updated at the same times as these other ones.
Also, could you update the file that tracks bigger dependency updates (.npmupgrade
) to point to MM-45255 as the ticket for the next round of React upgrades? There's a bunch of entries that refer to this ticket since those were for React 17
/e2e-tests |
Successfully triggered e2e testing! |
E2E tests not automatically triggered, because the PR is not in a mergeable state. Please update the branch with the base branch and resolve outstanding conflicts. |
package.json
Outdated
@@ -16,12 +16,12 @@ | |||
"@stripe/react-stripe-js": "1.6.0", | |||
"@stripe/stripe-js": "1.20.3", | |||
"@tippyjs/react": "4.2.6", | |||
"@types/color-hash": "1.0.2", |
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.
0/5 can we move it dev dependencies, since all our @types
are there
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.
As @hmhealey have mentioned we also need to remove react and react dom from .npm-upgrade.json
@hmhealey @M-ZubairAhmed updated |
@@ -153,7 +153,7 @@ | |||
"css-loader": "5.2.6", | |||
"dotenv-webpack": "7.0.3", | |||
"enzyme": "3.11.0", | |||
"enzyme-adapter-react-16": "1.15.6", | |||
"enzyme-adapter-react-17-updated": "1.0.2", |
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.
I didn't realize Enzyme didn't support React 17 (enzymejs/enzyme#2429) or 18 (enzymejs/enzyme#2524) itself, and that it hasn't been updated in quite a while (the last release of Enzyme was in December 2019). I'm going to file a ticket to start investigating switching away from Enzyme since it seems like it's no longer being properly supported
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.
@nevyangelova @jgilliam17 When we do QA review on this, would you mind spending some time trying to break the LHS menus and the drag and drop in it? I still can't remember exactly what the issue was with React 17 when I previously tried to update, but I think it was one of those two things |
Successfully triggered e2e testing! |
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.
Big change coming in wohoooo :D
tested, worked as expected for me. |
Test server destroyed |
Summary
Upgrade React to 17
Ticket Link
https://mattermost.atlassian.net/browse/MM-34187
Release Note