You can use babel-eslint [0] and the eslint-loader [1] to catch all errors babel might have.
Awesome, thanks!
I'm using pretty much the same setup, and the only trouble I have is that simple React exceptions can cause webpack-dev-server to terminate. It's not the end of the world, just kind of annoying to have to restart the dev server if I misspelled a variable!
I'm not sure if this is the same problem you've encountered, but if you find a solution I'm definitely interested. :)
Checkout the no errors plugin: https://github.com/webpack/docs/wiki/list-of-plugins
Are you using the babel-loader[0] for webpack? That generates nice errors right in the webpack prompt.
The experience has been fantastic compared to other static site generators (very limited control over display of content) or CMSes (too indirect for what is basically simple logic, especially around internationalization).
It was a bit fiddly getting everything set up so that React, React Router, React Intl, and Static Site Generator all played nicely together. But after about a day of banging my head on that, it's just worked ever since and been a dream.
If I could ask for one improvement: right now the build first runs the code through Babel and then runs that through WebPack. Problem is, if parts of the Babel build fail, there's no error reporting, and instead I get a WebPack-stage error about some file not being available. I then have to manually run the file through Babel to see that there's a simple syntax error.
[0] https://github.com/markdalgleish/static-site-generator-webpa...