In the past year, JSHint has deprecated several rules, stating:
Warning This option has been deprecated and will be removed in the next major release of JSHint. JSHint is limiting its scope to issues of code correctness. If you would like to enforce rules relating to code style, check out the JSCS project.
JSCS accepts over 150 configurable rules to support your team’s stylistic tastes.
Migrating from [ESLint]? Use the Crockford preset!
JSCS linting is meant to work alongside our JSHint linting.
You can enable or disable JSCS linting, or reference your own config, by editing .hound.yml in your repo.
Unfortunately, we don’t support custom additional rules yet.
Like the rest of Hound’s architecture, Hound’s JSCS linter is also open-source!
We think Hound is the best way to add style-checking to your workflow. Since it’s free for open source projects, it couldn’t be easier to get started.