SebastianVerified account

Darn, @JSHint is basically unusable if you're using stage 0 language features. That's a shame. I wish they would follow the lead of @babeljs

This will ultimately be the nail in the coffin for @JSHint. @babeljs-compatible tools will eclipse it in popularity, if they haven't already

@mjackson FWIW (roughly) over 1/3 of ESLint users use babel-eslint. In the future ESLint won't even be required as it'll be rolled into core

@sebmck we'd love to work with you to see what extension points you'd need to not need to rebundle in this way. @mjackson

@geteslint babel-eslint is a mess of monkey patches and will never provide a truly first class experience @mjackson

@geteslint Which means it either needs to be rolled into core, whether Babel or ESLint @mjackson

@sebmck I think it's just a matter of understanding what ESLint needs to make available to plugins to hook into.

@slicknet The issue is that nothing is made available to parser plugins.