update nodemon => fix security issues from dependencies

[FelixFurtmayr]

Hi,

thank you for the package :-) Just updated the nodemon version as npm audit shows me some vulnerabilities from this package which do no longer occur with the newer version. Would be nice if you could update the package. Thank you.

Regards Felix

[FelixFurtmayr]

well - just thought the test would pass ;-) but the node version was really old. so I updated the test and used another more popular (and working) version of the md file linter. now everything should be up to date again.

[FelixFurtmayr]

Hi guys, could you give me write access to the repo, so I can merge the stuff on my own? I see that you have no time to work on the project. I don't have much time either, but I can offer to update a project like this twice a year. Of course I can create my own version of the package, which is up to date. But I prefer not to mess up npm. Regards Felix

[hthetiot]

@ChrisWren any chance to merge/publish this fixes and give access to @FelixFurtmayr ?

[hthetiot]

Published fork with this fixes here @baladins/[email protected]

• https://www.npmjs.com/package/@baladins/grunt-nodemon
• https://github.com/Baladins/grunt-nodemon/commits/master

@FelixFurtmayr i invited you on the npm and github with write access.

[FelixFurtmayr]

Hi hthetiot, thanks for the innitiative :-)

I suggest we change the package name then to "grunt-nodemon-latest" and publish it on npm - what do you think?

[hthetiot]

well, i wanted "grunt-contrib-nodemon" but was taken, i prefer using @baladins/grunt-nodemon since i use this github org to maintain dead packages. and only the prefix change not the package name.

[FelixFurtmayr]

I'm fine with @baladins/grunt-nodemon.