-
Notifications
You must be signed in to change notification settings - Fork 920
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
React version 16.14.0 have reached it's EOL and require upgrade #3275
Comments
@shubher13 EOL is a little bit of a misnomer for react based on their versioning policy https://reactjs.org/docs/faq-versioning.html. that being said for your usecases react 16 is a valid blocker. I don't know if we have investigated the effort in migrating react to any of the newer versions but it should not be too difficult since react has a very clear migration path for it's versions. The bigger challenge however is that react 16 is a hard dependency for plugins based on our existing architecture. Changing that would be a breaking change and require a major release right now. Can you tell me what react features you need for your plugin? |
@shubher13 Is this still an issue that's blocking you? |
My understanding is that upgrading to React 18 is blocked by #1118. On the other hand, upgrading to React 17 would be fairly straightforward. But because it's a breaking change, it's probably worth going all the way to 18 anyway. Resources for upgrading to React 17: |
@joshuarrrr, As node v17 has already reached it's EOL so now it would be worth considering node v18 for the upgrade. Do you have any insights regarding the anticipated timeframe for this upgrade? |
we build custom plugins for OpenSearch-Dashboard which uses react version >=17, so while building the plugin with dashboard running with react version 16, it fails with conflicting dependencies.
So please let me know if there is a way to build the plugin with react^17 on osd running with react^16.
The text was updated successfully, but these errors were encountered: