Closed lmartins closed 10 years ago
Btw, if I run the task manually (outside of the watcher) but still lazy-loading the plugin, I get the correct behaviour:
Didn't worked before, it does now. Not sure what changed. Closing now.
Thanks for the report. Please reopen if you notice odd behavior again.
Hi,
I've been using grunt-newer pretty much everywhere but recently had the need to add an extra layer to my gruntfiles as they were becoming pretty slow at times.
Im now using jit-grunt to load the tasks only as needed but this had an undesired side effect, grunt-newer now seems to do nothing, on every change all files get processed as if they were all newer.
This is most likely due to any misstep on my configuration, so I was wondering if you can help me identify where the problem is.
I've also noticed that the cache files are all zero bytes, perhaps the reason the process happens for every file everytime.
I've simplified my Gruntfile a bit to show how I am trying to use grunt-newer:
With this setup, when I change an image for example, i get the following output:![screenshot 2013-12-27 10 33 50](https://f.cloud.github.com/assets/151981/1814160/e7a4add0-6ee2-11e3-80c6-5de7b45cae39.png)