Closed zachsa closed 1 year ago
We could certainly add an watch-invalidation: 'delay'
field to a task. Perhaps supporting none
would allow tasks which don't change when used in watch mode as well.
I believe this was implemented, but please reopen if I'm wrong.
I have the following workflow:
But currently the chomp task runs immediately on file save, and then is aborted and restarts on the prettier save. Could
chomp
support debouncing?In this case the chomp task would run x ms after the last time a watched file is saved (say 100ms). This is similar to the nodemon
--delay
option