Closed NullDivision closed 8 years ago
@NullDivision, I had the same problem. I just forked, updated and published v0.5.0 here:
If you fork you should probably make an even effort dude. Check pull request #65 for a proper fix.
The problem is that https://github.com/remy/nodemon doesn't specific a version in their package.json so tools like outdated don't pick it up. I just bumped nodemon to v1.7.1.
Either way, use it or don't but no need to be so abrasive.
NPM-s versioning behavior relies on git tags if present so explicit version declarations (while useful) aren't mandatory.
I'm abrasive because:
I already did this a week ago for my own project. If your intention was to do take over the project, at least make an effort is what I'm saying.
@ChrisWren Could you pleas update the nodemon version pulled by grunt-nodemon ? Amon other problems, the currently imported version has big performance issues when running in git-bash (cf https://github.com/remy/nodemon/issues/624 ) I see a PR is already ready, so why not merge it ?
Sorry, just merged
The nodemon package is out of date as a dependency. Current working version is
v1.7.1
which has some dependencies that cause breakage in some scenarios.For example:
In the event that the user tries to install
grunt-nodemon
as a dependency alongsidemongoose
,grunt-nodemon
will requirenodemon
who requirestouch
. The version in the current dependency stack isv1.3.8
which bringstouch
0.0.4. The current dependency istouch
1.0.0.