no need to change your gruntfile configurations


grunt task to watch files without using or fs.watchFile


Having all sort of weird issues with grunt watch? This is because it currently uses an unstable node.js functionality -

What happend on my case

Im using grunt on a virtualbox dev server with Ubuntu 11.10 and Node 0.6.19. My host system is Windows 7. My project files are on a shared folder between the host and server When i update files on the shared folder it does not trigger the

The solution

DO NOT USE but solve it simply by polling for changes in the most basic/simple way. This might be more CPU intensive, and might not work in high loads with many watched files. But im not sure if the original watch task would do the job as well on this case. i just did not check.

How to use?

simple place the task in your grunt/tasks directory
use the command: grunt simple_watch (instead of: grunt watch)

NO NEED TO CHANGE grunt.js configurations (your gruntfile)!
as it keeps on using the "watch" config.