-
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@^17
#129095
Comments
Pinging @elastic/datavis (Team:DataVis) |
@spalger any idea on how easy this would be? Or any know blockers? |
I think getting to 17 should be pretty easy, but I feel like at this point we should just go to 18 which also doesn't have any breaking changes, just type issues I would expect. |
@spalger can we assign this issue to your team? I think datavis doesn't have enough knowledge and time to work on this task, if not, who can be the owner? |
I took a look at this and I think we need to wait a while more. So many of our dependencies haven't even been updated to support React 17. An example of dependencies I'm concerned about:
If there is an urgent need from one team to get this going then, historically, it would be that teams responsibility to track down and get those dependencies replaced or pester/help get the upgrade done. |
FYI #128239 also exists |
Can we update directly to 18 since that is major Stable release? |
@damikun not until our deps are ready, many aren't even ready for react 17 yet. |
Describe the feature:
React
v17
was released over a 18 months ago on October 20, 2020.EUI has been developing against
react@^17
since elastic/eui#5584.There is really no
Team:
ownership of this type of widely used dependency so any team willing to lead this initiative please add yourTeam:
label.There seems to be very limited and specific breaking changes from
v16
tov17
relating to minor internal react implementations. See details in here.Required Dependencies
@elastic/eui
(React 17 eui#4800)@elastic/charts
(Compatibility with React 17 elastic-charts#1638)Last note is that
react@18
was released recently on March 29th, 2022 so it could be worth the effort to skipv17
altogether to maximize the benefit of this work.The text was updated successfully, but these errors were encountered: