add failing test
closed fswatchers no longer keep process alive

There was a slight race condition in `_handle` -- the method has
two async steps (realpath & stat), and before completion of either
of those steps, the FSWatch instance may have been closed. Previously,
even though the watcher was closed, new listeners would be added and
chokidar would thus keep the process alive. This behavior has been rectified.
Merge pull request #130 from chrisdickinson/close-ignores-further-events

Close ignores further events
Allow FS events if not on windows but polling not set to false

When `opts.usePolling` was null, but you were on a `canUseFsEvents` platform, `opts.usePolling` would get set to true, thereby negating `canUseFsEvents`. I feel this makes the defaults a bit more sane.
Merge pull request #134 from wraithan/patch-1

Allow FS events if not on windows but polling not set to false
Release 0.8.3.
fix stupid issues
Release 0.8.4.
Merge branch 'master' of https://github.com/paulmillr/chokidar