I'm surprised not to see generic tools on this list which make use of event-based file system notifications such as dnotify and inotify. See <a href="https://github.com/rvoicilas/inotify-tools/wiki" rel="nofollow">https://github.com/rvoicilas/inotify-tools/wiki</a> or inotifywait (<a href="https://superuser.com/a/959040" rel="nofollow">https://superuser.com/a/959040</a>) for examples.<p>I know this particular API (inotify) is specific to Linux (there might be similiar APIs on other OS). But it is awesome for all kind of build systems, for instance latex documents.
The origin of this list was when we were creating documentation for live-reloading code you write on your computer, and syncing those files to your cloud dev/staging environment directly. We then realised that there was no central repo of "live-reloading" tools for different languages/frameworks.<p>There's a slew of new tools coming out that are making this trend popular (skaffold, ksync, hasura). Some of which need your framework to have live-reloading and some don't.<p>I'm wondering what the HN community thinks about this general trend of pushing this write/test loop to a hosted dev environment. I think it's a response to increased complexity of bring up a full "microservices" environment on your local machine.
<a href="https://github.com/johnno1962/injectionforxcode" rel="nofollow">https://github.com/johnno1962/injectionforxcode</a> for IOS apps. I'd submit a pull request but i'm lazy.
Unless we are dealing with a list just strictly for frontend development(webpack/sass/etc), I'm kinda confused about the list. What about servers and daemons that perform "hot-reload" for you? And fsevents / inotify are the way to go, otherwise you will deal with 1~10+ seconds reloads, which can be miserable at times.