Kyle Robinson Young

@JamesMGreene Modifying that API runs the risk of making some plugins only compatible with `[email protected]` while others only `[email protected]`. If we are going to modify that API I'd prefer to...

> 1 How can we settle this once-and-for-all and improve grunt-contrib plugins RIGHT NOW? Fail as you have described but each contrib plugin has a `force` boolean option to override...

@sheldonh Thanks for the offer for help. It's likely something we should handle in the next version of Grunt to make it available to all tasks. We have the PR...

At the moment all the `grunt.file` APIs are sync. A large portion of the community expects them to be sync, so I think changing them to be async, is not...

If you change the internal function to be async, the user facing API also needs to be async. Consider the above example: ```js var matches = processPatterns(patterns, function(pattern) { file.glob(pattern,...

We've had plans to move to `chalk` instead of `colors` so it no longer pollutes the String prototype. The only issue is it would be a breaking change. So we...

@p1100i It would still be a breaking change as `'an error'.red` would break inside user's Gruntfiles.

There are a number of parameters that Grunt reserves: https://gruntjs.com/using-the-cli `version` is one of them. I recommend using another parameter name as this likely won't be fixed.

It could but at the moment, the library Grunt uses to parse the CLI parameters doesn't give ordering. So one would need to find one that does or write one,...

I'm not understanding the issue. Would you be able to create an example I could run that demonstrates the problem?