[Package Update] Switch from babel-eslint to @babel/eslint-parser to get latests fixes

[mrnossiom]

Hello there,

I ran eslint on my project and got an error, I searched on the internet and found that this was fixed in the latest version of the babel eslint parser but that they moved to another package name.

It went from babel-eslint to @babel/eslint-parser.

Could eslint-config-react-app switch to this new version ?

Here's a link that explain babel's decision: Babel Blog

Thanks for any answers...

MrNossiom

[mrnossiom]

Maybe I could have an answer...
I can see that I'm not the only one bothered by this.

I can do a PR to upgrade the package, just ask...

[agiveygives]

In the mean time, babel/babel-eslint#799 (comment) worked for me in fixing the cannot read property 'value' of null issue on builds.

[mrnossiom]

In the mean time, babel/babel-eslint#799 (comment) worked for me in fixing the cannot read property 'value' of null issue on builds.

Yes, but still, this package is not maintained any more and could break.

It will work as a temporary workaround...

EDIT: the PR #10761 is fixing that and should be merged in the next days or weeks.

[mrmckeb]

I'll close this off as I'm working on this right now and it will be released in 4.1.

Sorry it took us a while to get this out!