Hot module replacement not working with the default starter

[Kurren123]

Windows 10, Chrome 60.0.3112.90. I run:

gatsby new gatsby-site
cd gatsby-site
gatsby develop

I edit the file src/pages/index.js from <h1>Hi people</h1> to <h1>Hi people 123</h1>. No change is shown in the browser unless I refresh the page. No error is shown on the command line, only:

 DONE  Compiled successfully in 379ms                                                                                                                                                    9:40:47 AM

 I  Your site is running at http://localhost:8000
 I  Your graphql debugger is running at http://localhost:8000/___graphql

Only the following js errors are reported on the web page itself:

lowPriorityWarning.js:40 Warning: Accessing PropTypes via the main React package is deprecated, and will be removed in  React v16.0. Use the latest available v15.* prop-types package from npm instead. For info on usage, compatibility, migration and more, see https://fb.me/prop-types-docs
printWarning @ lowPriorityWarning.js:40
:8000/favicon.ico Failed to load resource: the server responded with a status of 404 (Not Found)

[dethi]

Hi,

• What is your current version of gatsby? (run gatsby -V in the root directory of your project)
• Did you try in incognito mode? (maybe an extension is blocking the websocket)

[Kurren123]

Hi @dethi. Still doesn't work after an npm upgrade or in incognito mode. My package.json file is:

{
  "name": "gatsby-starter-hello-world",
  "description": "Gatsby hello world starter",
  "license": "MIT",
  "scripts": {
    "develop": "gatsby develop",
    "build": "gatsby build",
    "serve": "gatsby serve"
  },
  "dependencies": {
    "gatsby": "1.8.4",
    "gatsby-link": "1.6.7"
  }
}

[Kurren123]

@dethi please also note that the react hot boiler plate example does work for me.

[billy-le]

I'm having this issue on a Windows environment.

gatsby develop boots fine. I just don't get any hot reload. When I change files, they are compile successfully but no hot reloading is done.

I'm on Gatsby 1.1.13 and using node 8.7

I used npm i gatsby-cli -g to install gatsby.

[thibmaek]

Can definitely back this up, does not work when installing from scratch.

[jamieguerrero]

I am also experiencing this issue with a previous gatsby project which HMR has worked for in the past.

[GramParallelo]

hmmm me tooo : / (as reference, hmr works on a clean install of create-react-app)
EDIT: upon further inspection - browser console outputs CORS error, could it be a wepack-dev-server issue?

[brandonjcreek]

I too am running into this issue when running gatsby develop from a Windows machine.

Node is currently at 9.2.0
Gatspy is currently at 1.9.118

Chrome is throwing the following error in console:
GET http://0.0.0.0:8000/__webpack_hmr net::ERR_ADDRESS_INVALID

[kripod]

@KyleAMathews The issue is that on Windows, localhost should be used instead of 0.0.0.0 for development. Since some update which happened during the last few days, all of my webpack-imported resources are being loaded from 0.0.0.0, which is incorrect for Windows users.

[mewdriller]

As @kripod mentioned, it looks like the issue is that program.host is coming in as 0.0.0.0 on Windows here.

[KyleAMathews]

This should be fixed now #2983

[thibmaek]

My issue was actually occurring on macOS High Sierra (latest stable).

[rdela]

@thibmaek same deal see #2960 (comment) for more

[Kurren123]

Hi @KyleAMathews. The issue still seems to be there. Windows 10 Chrome gatsby 1.1.27.