I am using static-site-generator-webpack-plugin [0] on a client project now and it has been fantastic. I have one json file full of all the data of the site and

I am using static-site-generator-webpack-plugin [0] on a client project now and it has been fantastic. I have one json file full of all the data of the site and then a bunch of components that render it in various ways. I've got translations in several languages plus the components can use React-Intl to get text, dates, etc. in the right format for the locale. 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-webpack-plugin https://github.com/markdalgleish/static-site-generator-webpa...