laxar-configure-watch: subsequent changes not always detected

[x1B]

Quick subsequent changes to individual files are not always detected. If a file is deleted or truncated and immediately written to again (e.g. by compass --watch), the delete-event is processed, but the subsequent file creation is ignored.

It seems that reducing the debounceDelay does help, but ideally we would not act on the delete-event at all.

[x1B]

This is related to shama/gaze#142

[x1B]

This will probably be fixed as soon as the debounceLeading option for gaze is available.
However, in the current state that option needs to be set to 'true' (string) to work (?!).

[x1B]

Closing this for now, as this won't be a problem when using Compass through grunt-laxar-compass (watcher thread will we blocked as long as compass is running). Also, hopefully gaze will be updated in the future to address this issue through the debounceLeading option.