Local dev setup triggering multiple reloads

[crisbeto]

When recompiling a file during the serve:devapp, the dev server triggers multiple reloads. The same is true when running the unit tests. This can be somewhat disruptive when debugging unit tests since it ends up running them multiple times in parallel.

[crisbeto]

I've been looking into this and it seems like it's more complicated than expected:

1. Karma doesn't have a proper way of debouncing file changes. There's the autoWatchBatchDelay option, but it only specifies how much time to wait from the first file change to when the browser reloads. I've tried playing around Karma's API in order to trigger the reloads manually, when the files are done, but I wasn't able to get it working.
2. None of the Gulp servers with livereload seem to have the option to debounce. Some allow you to trigger a livereload at a certain time, but that would require going through and adding a callback to each of the build tasks, which may end up being hard to maintain.