Hot reload of markdown files not working

[rcoedo]

I just installed gatsby for the first time and followed the examples found here. The page loads but when I make some changes to one of the markdown files I need to manually reload the page.

It seems to be some kind of CORS problem.

XMLHttpRequest cannot load http://0.0.0.0:1418/info?t=1448531803680. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:8000' is therefore not allowed access. The response had HTTP status code 404.

Thanks for such a nice tool!

[KyleAMathews]

Oh CORS. I can confirm this on a fresh install of Gatsby in a Linux VM. Can't reproduce in my Mac install. Investigating...

[rcoedo]

I'm using osx El Capitan and node 5.1.0 if that helps. I tried older versions of gatsby and older versions of node but I get the same behaviour.

[syrusakbary]

@KyleAMathews I can reproduce this in OSX too :( node v5.0.0

[KyleAMathews]

Ok, I can reproduce on my mac by deleting node_modules and reinstalling. Which suggests one of our lovely dependencies changed something...

[KyleAMathews]

Arggg... it was this webpack/webpack-dev-server#302

Downgrading webpack-dev-server to 1.12.1 fixed the problem... investigating why sockjs would cause trouble...

[KyleAMathews]

Apparently a known problem webpack/webpack-dev-server#326 and webpack/webpack-dev-server#328 I'll release a new version of Gatsby downgrading webpack-dev-server and do a new release once webpack/webpack-dev-server#328 is merged and I've confirmed it's fixed.

[KyleAMathews]

Fixed in 62fff69

Released 0.7.3

[rcoedo]

Yay! thanks for the fix.

[SpaceK33z]

@KyleAMathews, webpack-dev-server v1.14.1 has been released, which should fix the issue. It could be interesting to upgrade, since sockjs is much lighter than socket.io (doesn't have native build deps).