@ariporad is this up to date with master? It looks like it's failing Windows CI.

Also, it looks like something is undefined in run-tests.js

@nfischer: It's up to date with master, but the lint stage is failing _badly_

@nfischer: Oh, actually, spawnSync isn't available on node v0.10. Fixed.

@ariporad I changed the milestone, since I don't think we should push off 0.6 just so we can switch lint tools

I'm willing to help with this. Have you tried using the --fix option to get some of these fixed autoamtically?

@BYK: Oops... I forgot about that.

@BYK: Fixed.

Adding the following to the rule set helps a lot:

"spaced-comment": [2, "always", { "markers": ["@"], "exceptions": ["@"] }]

Looks like this is the problem:

/home/travis/build/shelljs/shelljs/test/which.js
18:5  error  "result" is already defined  no-redeclare

FYI I didn't try to fix all warnings so the warnings are expected. no-param-reassign is extensively violated and requires some fundamental changes in a few places so I didn't bother fixing them.

Also I'm not sure AirBnB style guide was a good choice since it looks a bit too browser oriented.

(Please do one file per PR)

lol - sorry for not following this :D

Don't worry, it didn't end up making a difference.

Umm… is there a reason why this is high priority?

I feel like this should be a low priority issue. Lengthy chores probably shouldn't be high priority. I think only in-demand features and bug fixes (and issues blocking those) should be high priority

Oh, yeah, that was a mistake. Fixed.

@ariporad any further work on this? This might be nice to start transitioning to using.