I have written a Flux-like framework called Redux that, in my view, preserves the best properties of Flux, but also fixes a few problems with it. In Redux, instead of Stores, you describe everything with “reducers”—pure functions with (state, action) => state signature.
This allows us to have hot reloading for everything: Stores (really, Reducers), Action Creators and Components. In fact Redux makes it possible to build developer tools like “time travel” debugger that also take advantage of hot reloading. I'm going to demo this in my talk at React Europe. Of course, Redux works on client and on server—it's universal.
Would you be interested in porting this kit to use Redux? In JS land, per-module hot reloading is a unique feature of Webpack, and it would be cool to truly show off its power.
I have written a Flux-like framework called Redux that, in my view, preserves the best properties of Flux, but also fixes a few problems with it. In Redux, instead of Stores, you describe everything with “reducers”—pure functions with
(state, action) => state
signature.This allows us to have hot reloading for everything: Stores (really, Reducers), Action Creators and Components. In fact Redux makes it possible to build developer tools like “time travel” debugger that also take advantage of hot reloading. I'm going to demo this in my talk at React Europe. Of course, Redux works on client and on server—it's universal.
Would you be interested in porting this kit to use Redux? In JS land, per-module hot reloading is a unique feature of Webpack, and it would be cool to truly show off its power.