Closed koistya closed 8 years ago
+1
+1 because its really sweet
Maybe -1 because it adds avoidable complexity to a starter kit. It either should be well documented / commented to remain starter friendly, or you might consider making it optional and convert the starter kit to a yeoman generator.
Definitely this. Do you need help tackling any of these things?
Trying to figure out, is there a way to use both Browser-Sync and React-Hot-Loader..
Why use BrowserSync over Webpack? It can handle CSS just fine.
@gaearon with BrowserSync you can open your website in different browsers and even on different devices (it creates HTTP tunnel with external IP to make things simple for connecting from devices other than your local PC), then when you navigate through the site, all the click, scroll, form data events are synchronized accross all the connected browsers which makes testing in different browsers supper easy.
Check this article by Addy Osmani http://addyosmani.com/blog/browser-sync/ Also these slides: https://speakerdeck.com/addyosmani/front-end-tooling-workflows
I get it now, thanks! That's a nice tool.
:+1: Here are some slides of a local presentation about that topic. Isn't very detailed, but enough for me to be excited about it :) http://okonet.ru/slides/reactive-development/
React Hot Transform was integrated into the starter kit. It plugs into the app when you run the site in a "watch" mode by hitting npm start
(see tools/start.js
).
http://gaearon.github.io/react-hot-loader/