Closed jdoose closed 9 years ago
Sorry, further investigation showed that it was full and completely my own fault. I missed that it is stated in the doc, that the "watch" option is additional to the current directory. I thought it would replace the default.
No bug. Closing issue.
when using grunt-nodemon on Win7 64Bit I experience high cpu usage (~100%). Watch-Option is set and respected, watching 32 files in 4 folders.
Research: If I see it right, then currently grunt-nodemon uses nodemon in Version 1.2.x. When I manually manipulate the grunt-nodemon package.json file to use nodemon in version ~1.3.0-5 then the cpu usage is at a minimum as expected
So I guess, it is merely an update to the package.json-file.
Thanks and regards,
Jens