Required for gulp / grunt watch bump

[shama]

• Scripts to package pre-built binaries
• Fire different events across multiple instances Ref Events firing across different watches/patterns #104
• Publish fixes with pre-built binaries

---

Above issues are fixed in navelgazer and implemented in the navelgazer branch here. Just a few skipped tests to fix.

[meinaart]

@shama: our latest fixes should take care of point 2 right? Is point #3 already done? I am very anxious to upgrade grunt-contrib-watch because it's really hogging my CPU all day.

[shama]

@meinaart It doesn't. That is a different issue than what your PR addressed.

FWIW, you can increase the options: { interval: 500 } in grunt-contrib-watch and that might alleviate some of the CPU usage for the time being.

[meinaart]

GH-104 should fix the issues with events across multiple instances right?

Thanks for the tip :).

[heycalmdown]

Is this still alive issue? I'm having trouble with constant CPU usage with Gulp. Or can we navelgazer in production instead?

[polybuildr]

Ping?