NOTE: In April 2016, JSCS maintainers [[ https://medium.com/@markelog/jscs-end-of-the-line-bc9bf0b3fdb2 | joined ]] the ESLint team. Plans for making the migration easier can be found at http://eslint.org/blog/2016/04/welcoming-jscs-to-eslint
We should decide weather to switch from jshint and jscs to eslint for our linting and code styling
I read here http://www.sitepoint.com/comparison-javascript-linting-tools/ the pros and cones of each of the three and the winner was eslint since it does both and is pluggable meaning you can create your own plugin for it.
**Steps to reproduce**
* The website is at http://eslint.org/
**Actual results**
* Feature request so currently no problems.
**Expected results**
* We should decide weather it would be good to switch.
There is a grunt plugin https://github.com/sindresorhus/grunt-eslint
This task is for the mediawiki core, extensions, skins.