SebastianVerified account

@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

@slicknet and just be cumbersome to maintain.

@sebmck what I'm saying is, why not work with us on this problem? It could make ESLint better and free Babel from such concerns.

@slicknet Babel is always going to have to be concerned about it though? Experimental/non-standard syntax is always going to exist.