Stackfilter fix: Don't remove modules/components from stack trace in the browser

[danielstjules]

Followup to #1766 and #1767

Makes the behavior consistent in the browser. We now only filter out mocha's own function calls, and don't touch calls from dependencies. Given how modularity is embraced in the node community, I think this is ideal.

[aaronjensen]

This is a good default, though it'd be nice if there was an option that came w/ this. I can imagine chai, other matchers, react, etc all muddying up stack traces.

[danielstjules]

Agreed - assertion libraries will get noisy as well. :) But this just makes things consistent across node/browser envs.

As for configuration, that's where things like https://www.github.com/rstacruz/mocha-clean can come in handy. It doesn't need be in mocha's core. Though I personally wouldn't be opposed to it.

[aaronjensen]

Oh, didn't know there was a mocha-clean. I'm good w/ it being external, though maybe a link in the readme/docs if it's not there already

[ArtemGovorov]

Didn't know about mocha-clean either, thanks for the hint. + 1 to @aaronjensen - a link in readme would be very nice to have.

[danielstjules]

I guess it could be added to the wiki :) https://github.com/mochajs/mocha/wiki

[danielstjules]

+1? @boneskull

[dasilvacontin]

Sweet, thanks @danielstjules!