SebastianVerified account

@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.

@slicknet Babel already has a lot of very sophisticated static analysis APIs and will get integration with Flow to make that even better

@slicknet so the next logical step is to just support listing in core. Once that happens then babel-eslint won't be necessary