Update chokidar to the latest version 🚀

[greenkeeper]

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 2.0.3 of chokidar was just published.

Dependency	chokidar
Current Version	2.0.2
Type	dependency

The version 2.0.3 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of chokidar.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

---

Commits

The new version differs by 7 commits.

• 925b534 Release 2.0.3.
• 545e16f Merge pull request #695 from clmystes/patch-1
• 3fdb7bd chore: upgrade to fsevents: ^1.1.2
• dac69b6 Merge pull request #687 from BridgeAR/fix-no-callback
• df88ff0 Add callbacks to fs.close
• a95a1f8 Merge pull request #682 from caseywebdev/unlink-and-readd
• c821fab Add failing test case for unlink and re-add

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper bot 🌴

[coveralls]

Coverage remained the same at 35.557% when pulling c002ed8 on greenkeeper/chokidar-2.0.3 into 6a10b9e on master.