Kyle Robinson Young
Kyle Robinson Young
My guess is it's from `tiny-lr` and specifically this: https://github.com/jshttp/on-finished/blob/master/index.js#L65 FWIW, this kind of bad stuff happens when you globally apply an es6 library. Why not just use babel when...
Thanks @tikotzky. That is very strange though, I'm curious to know where it's getting tripped up.
Try `grunt watch --verbose` and make sure it is watching files and operating normally on it's own. It should run fine after async tasks.
`grunt watch --verbose` should list the files it is watching. If it doesn't list any files then it's not watching any. Double check your file patterns.
The tests for this plugin use async tasks as well as a great deal of Grunt tasks are async, I don't think that is the issue. I also just double...
It should default to all cli args passed grabbed from `process.argv` itself: https://github.com/gruntjs/grunt-contrib-watch/blob/master/tasks/lib/taskrunner.js#L160 I'd accept a patch that merged `grunt.option.flags()` as well though. Thanks!
Which OS/version? Are you running under a proxy or behind a firewall?
No idea sorry. Let us know here if you figure it out.
We're using [tiny-lr](https://github.com/mklabs/tiny-lr) as the live reload server under the hood. You can try using that directly to isolate the issue.
Sounds good to me.