I’m not sure what you mean because React Router has absolutely no relation to Redux.
Dan Abramov

It’s not related to Redux specifically, but the way that React Router renders pages doesn’t make it obvious how to pass state from one route to another, or from root component to a route.

<Router history={browserHistory}>
<Route path="/" component={App}>
// it's very awkward to pass state from / to /about,
// because you have to use React.cloneElement()
<Route path="about" component={About}/>
), document.getElementById('root'))

Maybe this is one of the moments when people go for something like Redux. But this is probably something React Router docs should clarify, like you said, it has nothing to do with Redux.

Btw, lol at these Google results.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.