Watching files today is a bit hard, and it doesn't do it right. The current stack uses nodemon, but that's a bit too simple to our needs. Let's get ambitious.
What doesn't work today
Changing HTML files won't trigger an update, and that's needed specially because we deal with server-side rendering.
It's not possible to trigger a reload manually. Nodemon provides the rscommando, which restarts the server, but piping the output makes that unavailable.
Error won't show up in the output, which is bad for development.
Browserify compilation errors won't show up on the dev console
The happy land of development
Any file change (HTML, Javascript, CSS, Yaml) should trigger a server restart.
Too many restarts will put a heavy burden on the dev machine, so waiting a couple milliseconds to account for css compilations and the like should be there.
A way to control the node instance, being able to reboot it, change modes and the like.
Watching files today is a bit hard, and it doesn't do it right. The current stack uses
nodemon, but that's a bit too simple to our needs. Let's get ambitious.What doesn't work today
rscommando, which restarts the server, but piping the output makes that unavailable.The happy land of development