-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move to ESLint for JavaScript linting and code style checking #609
Comments
SGTM |
@fippo WDYT? |
@samdutton did you plan adding this yourself? |
Yes — though happy if anyone else wants to :). On 19 August 2015 at 08:33, Christoffer Jansson notifications@github.com
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think we should probably move to ESLint for JavaScript linting:
http://eslint.org
https://www.npmjs.com/package/grunt-eslint
Haven't used it myself, but it's quite popular among Chrome Dev Rel.
Pro and con:
http://blog.lauritz.me/linting-javascript-in-2015
http://www.sitepoint.com/comparison-javascript-linting-tools
Should be able to get rid of JSCS and JSHint if we opt for ESLint.
The text was updated successfully, but these errors were encountered: