Low priority I think but...
From what I've researched, mocha usually uses a mocha.opts file, not a .json file.
As we're expecting a json file instead, the format and location of this needs to be documented for users/devs along with what options are/aren't supported.
At a minimum if there's no expectation that an end user will modify the defaults set by this plugin it's possibly worth suppressing this message in TestFrameworks/Mocha/mocha.js
Low priority I think but...
From what I've researched, mocha usually uses a mocha.opts file, not a .json file.
As we're expecting a json file instead, the format and location of this needs to be documented for users/devs along with what options are/aren't supported.
At a minimum if there's no expectation that an end user will modify the defaults set by this plugin it's possibly worth suppressing this message in TestFrameworks/Mocha/mocha.js