Anuj

@grahamd711 Also, seeing this suddenly. Did you find a fix for this?

@grahamd711 None yet :( I upgraded RHL, Webpack, etc but no luck yet. Searching online it suggested that it might have something to do with `nodemon` but that isn't something...

Update: I found the problem with the Chrome error above. It was happening because Ghostery blocks polyfill.io by default. Here is the tracking ticket for that: https://github.com/Financial-Times/polyfill-service/issues/1426

Has anyone got this repo to work with React DevTools on Firefox? It seems like I can't get the right CSP setting that Firefox likes - any ideas or anyone...

@ctrlplusb keep us posted on the beta testing as well!

@diondirza @unleashit how is this working out for you so far? Good to merge or are there known issues?

@dhruvparmar372 @sinwailam193 @slipo what solution did you folks end up with here?

@designspin is there a gist you could share if it all works? Btw, here is the main issue on styled-components where you could also maybe post that update for others...

Wondering if anyone here has figured out a solution to this FoUC yet? @ctrlplusb Would you consider hiding the DOM node with the app until style has loaded in 'development'...

@strues It seems like it shouldn't be happening with styled-components according to [these comments in that repo](https://github.com/styled-components/styled-components/issues/386#issuecomment-333290785)?