Closed liouh closed 9 years ago
Hmm, I think the provided component
would always be the current proxy component. Not sure it would ever be null, since otherwise it wouldn't be transitioning away from it.
Not a common case, but I did get a null component when redirecting with this.replaceState() in componentWillMount. Came across it when trying workarounds for not being able to use renderUnavailable -- will open a separate discussion for that when I have enough info.
We hit this in a certain case as well. I think if the user is leaving before the component finished loading or something. I'll go ahead and merge.
Pushed 0.2.3
Didn't come up in my test scenario, but best to be safe.