use semistandard directly

[kt3k]

This PR simplifies the lint tool dependencies by using semistandard directly.
We don't need to keep track of each peer dep of eslint-config-semistandard anymore by this change.

---

closes #2633

[Munter]

This looks like a great simplification. I am wondering about the collapsing of all config into package.json though. Previously there was a separate configuration for lib/browser, which is now gone. Obviously the linting passes with the new changes, but have the rules accidentally become more lax because of that specific config removal?

[kt3k]

I admit that rules of envs are a bit relaxed by this change.

I updated the PR at least not to apply the test settings (like env: ['mocha']) to source files, but this is still a bit relaxed because it allows node variables (for example process global) in lib/browser.js etc. I think that is current limitation of semistandard (or standard-engine) and not possible to configure. So there remains some tradeoff between maintainance cost vs lint precision.

[Munter]

Lets get this in. Can you rebase this branch for us?

[ScottFreeCode]

Something that just occurred to me (but this doesn't need to be held up investigating it): could we use directives in the comments to take Node variables back off the ignore list for the browser file, the way one can use directives in the comments to add variables to the ignore list for specific functions or files?

[kt3k]

@Munter

Can you rebase this branch for us?

Done!

@ScottFreeCode
I'm not sure about 'ignore list', but if it means the list of global variables, we can use the directives like /* global foo */.
http://eslint.org/docs/user-guide/configuring#specifying-globals

[coveralls]

Coverage remained the same at 78.926% when pulling bb70b18 on kt3k:feature/simpler-semistandard into f9acbf1 on mochajs:master.

[Munter]

@kt3k Thank you for the contribution!

[kt3k]

Thanks for merging!

[boneskull]

This is problematic. :( It's fine for command-line users, but it can impact integration with IDEs.

We also seem to have lost some rules. There are no more complaints about a lack of 'use strict' where there should be.

[boneskull]

The IDE/editor problem is thus:

IDEs & editors have support for ESLint. They may have support for standard, since it's popular, but not semistandard or xo or anything else less popular that wants to stuff its config in package.json.

That means the semistandard prop in package.json is ignored. Likewise are the settings specified on the command line in the Makefile.

[boneskull]

test/integration/fixtures/simple-reporter.js fails a lint check that wouldn't have failed before this change