Use fsevents 0.3.7 to avoid segmentation faults

[pmq20]

cf.

• Use vector instead of CFMutableArray; fix #52 fsevents/fsevents#74
• Segmentation fault fsevents/fsevents#52

[fengmk2]

^0.3.7

[es128]

This is unnecessary. ^0.3.1 will already install the latest 0.3.x automatically, and the only thing existing projects need to do is npm update.

[paulmillr]

Doesn't bring any disadvantages tho!

[nickdesaulniers]

if you can publish a new version number, folks reinstalling watchify will get unblocked, see: browserify/watchify#257 (comment)

[es128]

@nickdesaulniers shouldn't matter. npm update (or at worst rm -rf node_modules && npm i) should be sufficient to pull in latest fsevents.

master branch is failing tests in CI currently, want to resolve before the next publish

[nickdesaulniers]

yep, thanks!

[es128]

Doesn't bring any disadvantages tho!

Turns out it does. It confuses lots of users thinking they need to wait for us to publish rather than just updating deps and letting semver do its thing.