A few issues reported by ESLint #477
Comments
Are we going to be running eslint regularly? If so, we should add it as a devDependency so we're all running the same version. Does that sound ok? |
@chilts I don't think we're planning on switching to ESLint, it was just something I was checking out and ran against the various repos. |
Cool, no problem. Think I'll go read up a bit about jscs! :) |
https://github.com/mdevils/node-jscs initial .jscs.json file: https://github.com/pdehaan/picl-idp/blob/c7e7cd52d043ab103aecb0bd839db92d8c6c3f76/.jscs.json ESLint is pretty nice too, if you haven't checked it out yet. A lot of overlap w/ JSHint, but a bit friendlier to customize warnings vs errors. There was also word of ESLint integrating some of the style rules from JSCS. Although note that JSCS is not a replacement for JSHint, it's intended to be more of a companion which focuses on styling vs code quality. Or another one I've been looking at is Phantomas: https://npmjs.org/package/phantomas |
There is probably a lot of overlap (I hope) with the ESLint results above and the jscs results from #487. Let's punt this bug until Q1-2014 and I can clean up any results above that still exist after the Grunt jscs tasks are passing. |
closing as "old" |
39 problems
We can ignore the
Error - Unexpected token ILLEGAL
messages (33 & 34) since those seem to be due to the#!/usr/bin/env node
(see eslint/eslint#494). This should be fixed in future ESLint versions.And my local .eslintrc config file is:
The text was updated successfully, but these errors were encountered: