Add into 11.0.0 the fix from 10.0.2 to 10.0.3

[agalatan]

This PR just patches 11.0.0-beta.0 and versions it to 11.0.0-beta.1, in the exact same way 10.0.2 was patched and became 10.0.3

Problem:

• babel-eslint@10.0.3 is being super weird for me (both eslint 5 & 6), in some Flow "edge cases", by reporting no-undef. But miraculously, babel-eslint@11.0.0-beta.0 fixes that problem.
• Unfortunately, babel-eslint@11.0.0-beta.0 exhibits (for eslint < 6.2.0) the exact same issue as babel-eslint@10.0.2 did, which was fixed here: fix from 10.0.2 => 10.0.3

Solution:

• Looking in the code for babel-eslint@11.0.0-beta.0, one can see this code is missing.

• All I did in this PR was copy-paste, yarn, and version it to 11.0.0-beta.1

PS: This is my first PR

[tilgovi]

Just came here to do the same :-D

[mwiencek]

Any chance the wonderful maintainers can look into resolving this? :) I believe we had to switch to v11 beta to parse Flow's explicit inexact object type syntax {...}, but having no-unused-vars broken is unfortunate.

[kaicataldo]

Hi! Sorry for the radio silence. We are in the process of getting babel-eslint updated and are developing a strategy to keep it maintainable going forward. You can follow along here.

[JLHwung]

Landed in 11.0.0-beta.2

npm install --save-dev babel-eslint@next