SebastianVerified account

@sebmck I'd like ESLint to be extensible enough to deal with experimental features and alternate ASTs going forward.

@slicknet Still requires weird integration from the Babel side which is awkward when it can just be in-house and first class.

@slicknet What Im trying to say is no matter how good the Babel-ESLint integrat. is, itll never be better than Babel integrating with itself

@sebmck @slicknet but ESLint solves other problems outside of Babels core purpose. Pluggable rules, great linting documentation.

@ben336 Babel already does a ton of static analysis, that's all linting is. The APIs are already there. @slicknet

@sebmck @ben336 @slicknet Babel has APIs only for ASTs for own needs, while ESLint covers rather CST (tokens, whitespaces etc.)

@rreverser ESLint API is really simple. There's no real CST, just access to raw tokens. @ben336 @slicknet

@sebmck @ben336 @slicknet Of course - unfortunately no-one has "real CST" yet :) Still, it has different goals where it's more powerful.