I've made a proposal to match the other examples, and trying to solve most of the problems I've met with redux. In order to have more flexibility to implement my ideas, I've not used an existing library. This is still heavily inspired by redux and redux-react.
One of the main difference with redux is the absence of "unique global store". In order to achieve the "Fractal" goal, stores are limited to the boundaries of each "components".
I also introduced more complexity than the simple reducer of redux and the simple connect of readux-react. But I tried to have each piece with a simple API, and the freedom for various implementations to interact.
My current opinion about my proposal is that the library is powerful and flexible enough, but the application code is not easy enough to navigate. I'm not sure if it's because of the overall architecture or not.
The custom library code is in the engine directory. The application code in the app and modules directories.
More documentation can be found in the README.md and api.md.
Pull request for architecture proposal of #28
Reminder of proposal: