You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I've followed the samples (maybe I'm missing something).
When I run #npm run start-dev I can see nodemon executes and "watches" bundle.js and server.js
However, if I change any of my tsx, nodemon does not become aware of any change.
What's the best way for nodemon to become aware of this? Should "something" recompile and re-publish bundle.js and server.js whenever there is a change?
If so, nodemon is about restarting node server, but how can we achieve refreshing the browser automatically?
Thanks, very useful boilerplate
The text was updated successfully, but these errors were encountered:
Ok, I forgot about npm run build-dev srcipt, If we execute that and then run npm run start-dev it seems webpack will rebuild and as soon as it's done, the server.js will be modified and nodemon will restart the server.
The only missin piece would then be refreshing the browser automatically when this happens. I have seen examples about this somewhere (I'm new to modern front-end) but maybe this is not so simple when using server side rendering. If you could clarify this, it would be very helpful. Thanks!
Hi, I've followed the samples (maybe I'm missing something).
When I run #npm run start-dev I can see nodemon executes and "watches" bundle.js and server.js
However, if I change any of my tsx, nodemon does not become aware of any change.
What's the best way for nodemon to become aware of this? Should "something" recompile and re-publish bundle.js and server.js whenever there is a change?
If so, nodemon is about restarting node server, but how can we achieve refreshing the browser automatically?
Thanks, very useful boilerplate
The text was updated successfully, but these errors were encountered: