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
It looks like connected-react-router, which we are currently using, does not support react-routerv6, so it doesn't make sense to try to update to react-routerv6 at this point.
It is looking like connected-react-router is no longer in active development - there are a number of issues opened for it asking when support doe react-router v6 is coming, and none of them have responses from the maintainer.
An alternative that has been mentioned a number of times is redux-first-history, which I actually tried out back when I was upgrading other dependencies. I think that one works with react-router v6, so that might be the route to go. If so, we'll probably want to migrate first to redux-first-history from connected-react-router, and then update react-router to v6.
This is one of the remaining dependencies we have not yet updated due to changes needed. Getting to
v6
is a multi-step process:v4
tov5
. This should be a simple update.v5
to prepare for the update tov6
.v5
tov6
compatibility package, which will allow some of our code can continue to usev5
while we migrate others, incrementally tov6
.v6
, update tov6
.┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: