-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Upgrade to React@18 #209337
Upgrade to React@18 #209337
Conversation
Project deployed, see credentials at: https://buildkite.com/elastic/kibana-deploy-project-from-pr/builds/290 |
…act18-merge # Conflicts: # x-pack/solutions/security/packages/kbn-securitysolution-exception-list-components/src/exception_item_card/conditions/entry_content/__snapshots__/entry_content.test.tsx.snap # x-pack/solutions/security/plugins/security_solution/public/timelines/components/netflow/__snapshots__/index.test.tsx.snap # x-pack/solutions/security/plugins/security_solution/public/timelines/components/timeline/body/renderers/netflow/__snapshots__/netflow_row_renderer.test.tsx.snap # yarn.lock
💛 Build succeeded, but was flaky
Failed CI Steps
Metrics [docs]Async chunks
Page load bundle
History
|
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.
kbn-test
changes LGTM
Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services) |
Admin merged upon request |
Summary
This PR upgrades React packages to version 18, while keeping Kibana running in Legacy mode (
ReactDOM.render
). This is the first phase of the React@18 upgrade; the second phase will gradually migrate Kibana to Concurrent mode (createRoot
) (exact plan is tbd).Upgrade is intended to be non-breaking and behave just like React@17, but it still requires thorough testing from all teams that own UI to discover any potential critical UI issues. The testing was done in #203114.
Most of the breaking work was completed in previous PRs and this PR only includes minor breaking jest tests tweaks / snapshots updates
Backports:
Risks
Kibana’s UI functional tests coverage and significant manual testing that was done by a lot of teams in #203114 gives us a lot of confidence.
However, since this was a large internal change for React they still could be issues hidden in "remote" parts of UIs, think of blank screens, error splash screens, unresponsive pages, new errors in the console, unpredictable UI behavior (like laggy text inputs that skip letters when typing fast).