ducks-modular-redux | bundling reducers , action types | State Container library

I have been trying to implement react server-side-rendering using next, and i am using the with-redux-observable-app example, the example works fine, but i would like to improve the project a little bit by doing

1. redux modular pattern
2. fractal project structure
3. If possible, i would like to implement stateless components
4. Because #2, i can no longer use react state lifecycle, to solve that i usually took advantage of react router onEnter props, but this suggest that i should use componentWillMount, which doesn't meet my #2 condition

I have put the project on github, with this particular problem committed on this branch

Here's the summary of what i did so far

to achieve #1

I was doing a bit of refactoring and tried connecting a higher level component to redux using connect() but the component I'm connecting keeps giving me empty props.

I've included the relevant code, I've structured my redux reducers into a ducks format, so the actions/creators and reducers are in one module file.

The files are containers/login.js, presentation/login.js, presentation/logins.js, app.js and the root index.js.

When I decided to rename some actions, files and reducers, moved the connect to a higher component, the connection stopped working and now I have empty props.

Help much appreciated.

I've been structuring my redux bundles using the Ducks pattern and so far it's working really well. However, one use case that I haven't quite figured out is how I'm supposed to write thunks that dispatch actions from multiple different files.

For example, I have one redux bundle file that looks like

I am cleaning up my reducer setup which was wrong from the beginning. I using the redux doco and the ducks pattern to set it right.

I want to separate/divide my state like the doco suggests: