@denious Good to read that. I think '/' should be more robust for development so I just updated it :+1:

Thank you for a very well-written tutorial. Nowadays, many programmers choose React over Angular, even though Angular takes the first place in the list of JavaScript frameworks. But developers admit React is more convenient to use for many reasons (highlighted here in details: https://mobilunity.com/blog/migration-from-angular-to-react-developers/ ). First of all, React has much more simpler structure and less opinionated than Angular, thus, it is easier to learn and use React. Besides, React gives a lot of space for developers decisions and you could combine it with any other JS framework you wish.

I refactored it to break up the components with the Provider HoC. https://gist.github.com/wordyallen/fbd9e239656cb6232fc3bfbcfb987522#file-stop_watch_component-js

Only waiting for this from last one month :) Thank you

yes that is it

Good article! Just small question: isn’t using “actions: bindActionCreators(Actions, dispatch)” breaks the whole idea of container/component approach? Since you are using connect it actually creates another component for you, which is called a container, but for me it seems that you don’t have the presentational components, cause they are not dumb (meaning they know the logic of your app).

Would be good if you put the files tree and file names for each file. Except that, colors is not recognized anymore by webpack v2 in devServerschema and we now have to use babel-loader instead of babel. Other than that, still one of the best tutorials out there for using webpack-dev-server with Hot Module Replacement.