If reload is used with the --watch-dir option the browser gets reload instantly after a file-change occurs. This file-change might be triggered e.g. by a build tool, that empties the watched folder to refill it moments later with a new version of the app or web page. In this case the browser may reload the web page in an unready state which can cause errors in the browser.

To solve this problem I propose a new optional parameter --debounce wait which will postpone the reload until after wait milliseconds have elapsed since the last time a file-change occurred. This value could be st internally to 0 which would trigger a reload instantly on every change.

Opinions on this?