Abort due to warnings
micah66 opened this issue · 8 comments
I am having an issue where I run grunt retire, it fails and all that is listed at the end is "Aborted due to warnings". I have set up a file which receives all the logs when running grunt retire and from there I have pulled out all the logs which state that there is a known vulnerability, with a severity rating. In all cases the severity is either low or medium. I have tried updating those packages but this has not helped.
I think it should be noted that I am fairly new to development and it could be something simple I am missing. Any and all help is much appreciated. Thank you!
@micah66 I can't reproduce this issue. Could you provide logs and what version of npm and grunt-retire you are using?
Hello! I have similar issue with grunt-retire.
node - v10.14.0 ( on v8.14.0 all is ok ),
grunt-cli v1.2.0,
grunt v1.0.4,
grunt-retire - v1.0.7,
OS - macOS Mojave 10.14.3
Warning: Callback must be a function Use --force to continue.
Aborted due to warnings
I found bug - /node_modules/retire/lib/repo.js line 54 fs.unlink should be changed to fs.unlinkSync,
then node v10.14.0 working as well.
@Sunbus: Could you see which version of retire you have by executing npm ls | grep retire in the repository you have trouble in? Only 1.x is currently supported by grunt-retire.
Could you also checkout https://github.com/RetireJS/grunt-retire/ and run grunt there to see if that fails for you as well?
@kozmic: I checked it in my repository - grunt-retire@1.0.7, retire@1.2.13.
Result of grunt task running in cloned grunt-retire - screenshot.