Hidden Stack Traces

It appears that throwing an error from a gulp task will log the error message, and the task in question, but not the stack trace.

Is there any reason not to make logging stack traces the default behaviour? For the sake of minimising surprises I think it would be worth considering. It’s something that I know others have struggled with Grunt in the past as well: stacks are hidden behind a flag (--stack), and a few coworkers went a couple of weeks before discovering it was even an option, leaving some errors a complete mystery.

[laurelnaiad]

In case anyone stumbles across this and has trouble deciphering how it works, this is what works for me to get stack traces from all errors:

gulp.on('err', function(e) {
  console.log(e.err.stack);
});

[Taytay]

Thanks for the clarification @contra. Good to know.