grunt watch and async tasks

[ctalkington]

@cowboy we have a less task that is async but it basically kills watch when an error is ran into. we will likely just add an if to call done() after error so it can continue through. however it brings up the question, in the normal flow of grunt (ie direct commands vs watch) do you really want it to continue through?

if i recall watch has logic to catch warnings that are fired. its also my belief that the fail.warn would auto stop the code during the normal flow so maybe its a non-issue? just looking for some guidance of how you think grunt should work with watch and async.

[emilingerslev]

Not completly sure about the error/warning part, but I have also found out that watch and this.async() does not go well together. When all async's are done the watch process stops. I can't imagine that's correct behavior?

[tkellen]

We have a new watch task, which you can get by adding grunt-contrib-watch to your project deps and doing grunt.loadNpmTasks('grunt-contrib-watch') in your gruntfile. It should resolve this issue. If by chance it doesn't, can you please open the issue over on the watch task?