在Mocha测试中绕过ESLint的`no-unused-var` for Should

Question

I'm using ESLint on all my files, including the test files, with a no-unused-var: true rule. I'm using Should.js in my Mocha tests, and in one of the files, I'm getting an error on the should variable. A quick comparison to the other tests shows, that in other files I have at least one line that starts with should (ie should.not.exist(err); ), whereas in this particular file, I only use it in property form (ie a.should.equal(b) ).

Short of turning the rule off for the entire file, or coercing perfectly readable tests into the variable use of should , is there any way around this? Can I turn off the rule just for the should variable? Perhaps add an exception for it? Or (hopefully) a more elegant solution?

Answer 1

In this particular file you can just require instead of declaring.

var should = require('should');

instead do

require('should');

Answer 2

Well, doesn't seem like there's an elegant solution to this, but I think I came up with a close approximation: I just added a single line to my before() hook, stating simply should; . Since this evaluates to the should object, or in other words a "truthy" value, it can be treated as a no-op. The side effect is that now the should variable is "used", and ESLint does not throw a warning.

I'm going to let this answer hang for a while, hoping one of you has a better solution.

Per request, here's a gist showing the hack in action .