react-router VS isomorphic-redux

I'd like my React based SPA to render on server side (who's not these days). Therefore I want to combine React with react-router, redux and some build layer like isomorphic starterkit.

I'm building isomorphic application using ReactJS with react-router module for routing purposes on server side.

I have some react-router routes as follows:

(I originally thought it was a React Router Bug.)

I'm using react/react-redux/react-router/react-router-redux.

I am duffer when it comes to React-Router component. However I was not able to find explanation of why my components become unmount when I walk through links? And how to prevent it ?

I found this closed issue suggested using Router.ActiveState mixin and route handlers, but it looks like these two solutions are now deprecated.

I am new to react-router (https://github.com/rackt/react-router). I included it after react like this:

There is very good example of how to make a breadcrumbs on site in examples folder of react-router repo. But I'm wondering how to make breadcrumbs with dynamic routes.

I'm using React-Router 1.0.0-rc3 together with Redux-Router 1.0.0-beta3.

// MailListActions.jsexport function loadMessages() { return { type: 'LOAD\_MESSAGES', promise: client => client.get('/messages') };}// MailListReducer.jsimport Immutable from 'immutable';const defaultState = { messages: [], fetchingMessages: false };export default function mailListReducer(state = defaultState, action = {}) { switch (action.type) { case 'LOAD\_MESSAGES\_REQUEST': return state.merge({fetchingMessages: true}); case 'LOAD\_MESSAGES': return state.merge({fetchingMessages: false, messages: action.res.data || null}); case 'LOAD\_MESSAGES\_FAILURE': // also do something default: return state; }} As I'm using promiseMiddleware, LOAD_MESSAGES, LOAD_MESSAGES_REQUEST and LOAD_MESSAGES_FAILURE are dispacted as request /messages ends.