Stop using babel-eslint

[gaearon]

It is not necessary anymore.
We should migrate our source and examples to not use it.

[raspo]

wrong link? https://twitter.com/geteslint/status/714642903482564608

[gaearon]

Lol yeah, that’s the one.

[kennetpostigo]

@gaearon how come it is not needed anymore?

[gaearon]

From https://twitter.com/geteslint/status/714642903482564608:

The ESLint default parser natively supports ES2016, JSX, and object rest/spread. You don't need babel-eslint for any of that.

[kennetpostigo]

Awesome!
thank you @gaearon

[mwilc0x]

@gaearon would this require an update to the eslint-config-rackt dependency? I couldn't find the repository hosted anywhere on GitHub. Looking at the installed eslint-config-rackt package though, I do see "parser": "babel-eslint", in index.js.

[knowbody]

I'm working on this one, updating the rackt config to airbnb as this was requested somewhere already anyway, and eslint-config-rackt is not mainatined

[gaearon]

Yea.

[knowbody]

@gaearon do you have any preference for customizing eslint-config-airbnb? or just follow it as is? I will push WIP soon

[gaearon]

What about semicolons? I couldn't care less about whether we use them or not but I'm concerned about the amount of work it would take to convert docs back. On the other hand any changes to style would require tweaking docs anyway.

Can we just use eslint --fix and write a script to run Markdown embedded snippets through it as well?

[knowbody]

what about stuff like: vars-on-top, no-param-reassign?

[gaearon]

Ugh. I guess we'll have to use a custom config. vars-on-top doesn't make sense to me.

[knowbody]

same here. I would just make both of those disabled then. also I used eslint --fix before and it fixed semicolons.