Move to eslint (instead of both jshint + jscs)

[shakyShane]

@shinnn - I'm tried of using two tools for lint/correctness, eslint seems to do both - any experience?

[shinnn]

👍

Yes, I was just planning exactly the same thing, and happy to see you posted this issue. Recently I use ESLint instead of those two linters, whenever I create a Node module.

[shakyShane]

Ok cool - Are you happy to take this on?

[shinnn]

Sure. I'll check corresponding rules between ESLint and JSHint/JSCS, then create .eslintrc for this project.

[shakyShane]

Excellent - I also want to remove gulp too, so that's next on the list

[shakyShane]

Also want to swap mocha for tape, but that's a bigger deal given there's over 400 tests

[shinnn]

want to swap mocha for tape

+1000

[shakyShane]

I'll take that one on as I want a huge refactor for tests also

[IanVS]

Let me know if you guys need any help moving to ESLint. I don't have bandwidth right now to do a full PR, but I can help answer questions and address ESLint issues if you run into any.

[stevemao]

@shinnn You do that just because you don't wanna maintain two modules to lint? I do this mainly just for this reason as I found maintain two meta data files is just harder :)

[shakyShane]

@stevemao - It's simply reducing 2 tools to 1, nothing more complicated than that :)

[stevemao]

Just very surprised that you guys doing this for the same reason lol. Usually I like smaller modules with limited scope but this is one exception :)

[IanVS]

From a cursory search, I've seen several projects doing this. Nobody really likes the overhead of maintaining two essentially identical tools when one will do the job.

[shakyShane]

@IanVS - yep! And there's 1 feature in eslint that completely won me over when using it in other projects - when there's a failure, it gives you the exact rule name right there in the CLI output - no searching docs for rule names! ha!