You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
react-router-dom is moving towards version 7 and will be changing its package name to just react-router. Given this upcoming change, do we have any plans or movement to support the new react-router package in bridge?
Questions
Is there a migration plan?
Should we start accepting both packages?
What's the compatibility impact?
Suggested solution
Although I understand that the transition to v7 was designed to be to be non-breaking, I have concerns about the package name. I believe we should support both versions.
The migration to just react-router is inevitable. 🤔
Thanks for your feedback, we are aware of this issue too, we do need to be compatible with this change in the future, we will adjust the implementation of bridge to be compatible with react-router-dom v7, thank you again~
Clear and concise description of the problem
About bridge/bridge-react package
Current Situation
"react-router-dom": ">=4"
react-router
Issue Description
react-router-dom is moving towards version 7 and will be changing its package name to just
react-router
. Given this upcoming change, do we have any plans or movement to support the newreact-router
package in bridge?Questions
Suggested solution
Although I understand that the transition to v7 was designed to be to be non-breaking, I have concerns about the package name. I believe we should support both versions.
The migration to just react-router is inevitable. 🤔
Alternative
No response
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: