Update npm-watch to the latest version 🚀

[greenkeeper[bot]]

Version 0.2.0 of npm-watch just got published.

Dependency	npm-watch
Current Version	0.1.9
Type	devDependency

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

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of npm-watch. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

---

Not sure how things should work exactly?

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[coveralls]

Coverage remained the same at 34.746% when pulling 4d003df4e2c7ad1bec50b9fdf3b4517f60602381 on greenkeeper/npm-watch-0.2.0 into 03f122543690f2e7e5f1b4a5ca9eb366e93b989f on master.

[greenkeeper[bot]]

Version 0.3.0 just got published.

Update to this version instead 🚀

Release Notes

⬆

Update nodemon version

Commits

The new version differs by 4 commits.

• 559606e 0.3.0
• 9ea41ce Merge pull request #50 from sandrosc/patch-1
• 91fcfe7 Update package.json -> nodemon version
• faa56d7 Update package.json

See the full diff

[greenkeeper[bot]]

• The devDependency npm-watch was updated from 0.1.9 to 0.4.0.

Update to this version instead 🚀

Commits

The new version differs by 4 commits.

• d13a35d 0.4.0
• 93effc5 Merge pull request #57 from bluebrat/master
• e95f172 Merge pull request #1 from bluebrat/runOnChangeOnly-option
• f56cb5b Implement runOnChangeOnly option

See the full diff