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
A is initially rendered, then B is later rendered post navigation.
Actual Behavior
A is initially rendered, then there's no change post navigation.
There's no change due to the transition manager being bound in componentWillMount rather than componentDidMount.
I have a very small patch that resolves this and would allow me to migrate a large codebase heavily coupled to v3 to React 18 without dropping StrictMode. Short of this, I'll likely locally publish an internal fork of v3 with 18 compat. I am well aware that I'm asking to patch a years-old version of this package, but I wanted to check before forking.
The text was updated successfully, but these errors were encountered:
I'm also facing the same issue. And I can't really migrate to newer version because it's a big project using some unavailable features in the newer versions (like onEnter, onLeave). A patch of v3 with react 18 compatibility would be appreciated.
What version of React Router are you using?
v3
Steps to Reproduce
Load
/a
, navigate to/b
.Expected Behavior
A
is initially rendered, thenB
is later rendered post navigation.Actual Behavior
A
is initially rendered, then there's no change post navigation.There's no change due to the transition manager being bound in
componentWillMount
rather thancomponentDidMount
.I have a very small patch that resolves this and would allow me to migrate a large codebase heavily coupled to v3 to React 18 without dropping
StrictMode
. Short of this, I'll likely locally publish an internal fork of v3 with 18 compat. I am well aware that I'm asking to patch a years-old version of this package, but I wanted to check before forking.The text was updated successfully, but these errors were encountered: