Ben Alman

@jzaefferer what happens when jshint fails because of a syntactic error that prevents the tests from running, or causes them to hang in some way?

@jzaefferer what kind of message do you output when someone uses a deprecated feature or has configured the plugin in a sub-optimal way?

Overall, makes sense to me, Thanks, @shama for doing this. I do like the idea, though, of first implementing the warnings in verbose mode only, then in a subsequent minor...

I don't have any personal use-cases, but I know a discussion was happening around gruntjs/grunt-contrib-concat#59, and there might be others. If this is a common request, perhaps it should be...

@getify unfortunately, task names can be any arbitrary string. By giving the substring `--force` a special meaning it could cause compatibility issues. Technically. Unlikely, though. Either way, it feels more...

@shellscape could you explain all four "force" options? By "default" do you mean the current behavior?

I'm definitely not going to build-in a `force:` prefix, but you should be able to create a custom task that does just that. I encourage you to create it and...

So here's the problem. How do we know that an error is expected vs unexpected? For example, when a task fails, it's because an exception is thrown—and handled—but thrown nonetheless....

One thought is to look @ the paths in the stack trace, and if any of them exist outside of Grunt or your project's node_modules folder, dump the stack trace...

Right now, this is what happens for each file: 1. stat the file. if that fails, throw an ENOENT exception and burst into flames. 2. is the file a directory?...