Ability to filter out the stack trace

[lucassus]

Something simillar we could do in jasmine-node https://github.com/mhevery/jasmine-node/blob/dfa2e18517d8fbc5357489de643376eb5e303dfe/lib/jasmine-node/index.js#L128

It could be extremely useful for debugging failed scenarios written along with https://github.com/angular/protractor or other library. Currently stack traces contain too much details and it's hard to figure out where we should start debugging the failed scenario. For example https://gist.github.com/lucassus/de99d54cfb98c6ae60eb

[lucassus]

currently I use this dirty hack (reporers/base.js):

    // filter the stack trace
    var lines = [];
    stack.split(/\n/).forEach(function(line){
      if (!line.match("/node_modules/")) {
        lines.push(line);
      }
    });
    stack = lines.join('\n');

    // indent stack trace without msg
    stack = stack.slice(index ? index + 1 : index)
      .replace(/^/gm, '  ');

[lucassus]

@visionmedia do you have any thoughts about this feature request? If it's worth to have I could implement it.

[travisjeffery]

i don't think it's necessary. you could make your own filterable reporter, no need to hack the base reporter.

[rstacruz]

Hey guys, I've managed to implement this exactly, and published it as a new package. I found node_modules quite a nuissance too. It's simply used alongside mocha as --require mocha-clean.

https://github.com/rstacruz/mocha-clean

[hellboy81]

Is there possible to implement mocha-clean feature in mocha:

remove node-modules from stack trace?

[danielstjules]

#1766 We originally had it enabled by default