Open greenkeeper[bot] opened 7 years ago
devDependency
npm-watch was updated from 0.2.0
to 0.4.0
.devDependency
npm-watch was updated from 0.2.0
to 0.6.0
.Update to this version instead 🚀
Thank you to @kaycebasques, @Leo7654, @charlesbdudley for your kind contributions!
The new version differs by 11 commits.
efb3c75
0.6.0
ced6020
Documentation for verbose mode
e02147f
Merge pull request #53 from charlesbdudley/add-clear-buffer-option
a30560c
Merge branch 'master' into add-clear-buffer-option
f5f5064
Merge pull request #54 from Leo7654/master
22aef57
Merge branch 'master' into master
305a45e
Merge pull request #63 from kaycebasques/patch-1
6e88d57
Fix code samples
c555e38
Add section on ignoring files
3ba807e
Add verbose option
73b3c9d
added config flag to clear the buffer on file changes
See the full diff
Version 0.3.0 of npm-watch just got published.
The version 0.3.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.
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
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: