The 3REE Stack: React, Redux, RethinkDB and Express.js (opens in new tab)

In my React (+Redux) applications, Express only plays a very minor part of being the entry point for the server.

Check this out https://github.com/joshhunt/reactapus/blob/master/src/server.... Koa or Express.js wouldn't really make that much of a difference.

Fair point. I didn't really give this layer too much thought considering the focus of the blog. It could really be any Node.js framework.

Although saying that, if I had chosen Koa.js the stack would have to be called 3REK, or 3RKE :/

I think if you take a lot at the motivations that Dan Abramov had for creating Redux [1], you'll see that improving debugging was at the centre of it. Check out his talk he gave at React-Europe. He basically is talking about improving developer tools. The functional approach Redux takes allows for you to see state transitions and replay actions - making it relatively trivial (compared to say Angular.js) to understand how to reproduce a buggy state.

[1] https://github.com/rackt/redux

[2] https://www.youtube.com/watch?v=xsSnOQynTHs

Dude, this is half the point of redux. Theres a debugger that lets you visually step through every state of the store and your corresponding app - https://github.com/gaearon/redux-devtools

Please don't post dismissive comments to HN. A substantive point about the impact on debugging would of course be welcome.

It's not really a problem now.

I use the auto-transpilation trick with Babel. You can see a small example in my repo: https://github.com/odiroot/songs-to-spotify/blob/master/src/...

Then in required modules you're free to use ES2015.

You can use Babel with node on the back end. See https://babeljs.io/docs/usage/require/. Definitely not the most ideal solution, but it allows you to easily transition into ES6 when all the features land in node.

The article is about that.