Watch mode stops working after a while

[sanity-io]

Watch mode stops working after a while

[coreyward]

I've not noticed this happening as much since I filed this bug originally. If it's been overnight or longer, or if my computer goes to sleep, it's more likely, but that's not a dealbreaker for me.

One thing that you can do to get the listener working again (and refresh your content) without restarting your dev server is to enable the refresh endpoint in Gatsby and then send a POST request to it. To enable the endpoint you just set an environment variable named ENABLE_GATSBY_REFRESH_ENDPOINT to a truthy value. I do this in .env, but you can do the same running from the command line:

ENABLE_GATSBY_REFRESH_ENDPOINT=true gatsby develop

Once you do this, restart Gatsby and proceed like normal. When you notice your content isn't reloading, or if you want to pull fresh data from other non-live sources, send a POST request to http://localhost:8000/__refresh. I like to set this up in my package.json scripts for convenience:

"scripts": {
  "develop": "ENABLE_GATSBY_REFRESH_ENDPOINT=true gatsby develop",
  "refresh": "curl -X POST http://localhost:8000/__refresh"
}

Then you can just run yarn refresh (or npm run refresh) to get fresh content and re-enable the Sanity listener.

[dylanjha]

I'm seeing the same thing. @coreyward is this a new issue for you or has it always happened?

[coreyward]

@dylanjha It's been an issue since I turned on watchMode on November 22nd.

[fanniegunton]

Seeing the same issue using the sanity-gatsby-blog starter.

[roffelsaurus]

Also experiencing this. Both myself on localhost and our content editors previewing stuff with gatsby develop -H 0.0.0.0 on heroku. I have also turned off overlayDrafts.

[MantasMikal]

I have the same issue

[j0hnm4r5]

Confirming this is still happening on 1.150.

[bryangruneberg]

Thanks @coreyward - that's helpful!