React-static: *Still* not hot reloading

Created on 14 Oct 2017  Â·  4Comments  Â·  Source: react-static/react-static

Hello, I'm unsure why my previous issue was closed. I understand changing data will not cause the app to reload but changing CSS, markup, etc should. This is not the case, even with starting with the latest [email protected]. Please advise.

Most helpful comment

Looking into this.
On Sat, Oct 14, 2017 at 12:36 PM Joe notifications@github.com wrote:

Hello, I'm unsure why my previous issue was closed. I understand changing
data will not cause the app to reload but changing CSS, markup, etc should.
This is not the case, even with starting with the latest
[email protected]. Please advise.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nozzle/react-static/issues/45, or mute the thread
https://github.com/notifications/unsubscribe-auth/AFUmCYzMfQoYX46Lca3QKhzgA4AekOtvks5ssP8kgaJpZM4P5e50
.

All 4 comments

Looking into this.
On Sat, Oct 14, 2017 at 12:36 PM Joe notifications@github.com wrote:

Hello, I'm unsure why my previous issue was closed. I understand changing
data will not cause the app to reload but changing CSS, markup, etc should.
This is not the case, even with starting with the latest
[email protected]. Please advise.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nozzle/react-static/issues/45, or mute the thread
https://github.com/notifications/unsubscribe-auth/AFUmCYzMfQoYX46Lca3QKhzgA4AekOtvks5ssP8kgaJpZM4P5e50
.

@tannerlinsley @josephdburdick Just created #50 . As far as I'm concerned it seems to occur when the app is not running on port 3000

@coisnepe Interesting, maybe I force-quit an instance with terminal which had the process running? It didn't come to mind because afterwards I was able to use create-react-app to create a new app and test that hot reloading was working, and it did, on port 3000.

Since reading the above notification and #50 I restarted my computer completely, went back and ran my react-static test again and it worked. I'll let one of the contributors close this issue out because perhaps there's an underlying issue where a lost process will prevent this project's future processes from hot reloading. Thanks for looking into this.

Thanks for verifying!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

getDanArias picture getDanArias  Â·  4Comments

tomagladiator picture tomagladiator  Â·  3Comments

calvinrbnspiess picture calvinrbnspiess  Â·  4Comments

RAMTO picture RAMTO  Â·  4Comments

lottamus picture lottamus  Â·  3Comments