Parsing error: couldn't resolve `eslint` babel-eslint@8.1.2

[joshuaalpuerto]

Hi am not sure if this issue goes here. But when im running test on my CI its failing due to:

standard@10.0.3
babel-eslint@8.1.2

I have to revert back to babel-eslint@8.0.3 to make my test pass.

Cheers!

[timoxley]

I'm seeing a similar issue. Using babel-eslint@8.1.2 my editor (vim + ALE) reports "x is not defined" for class fields (static and instance). I get the same error running standard on the command line:

npx standard …/View3D.js
standard: Use JavaScript Standard Style (https://standardjs.com)
  …/View3D.js:6:10: 'propTypes' is not defined.
  …/View3D.js:10:3: 'viewConfig' is not defined.

Note this is a different error to not having any "standard.parser" value set in package.json.

After installing babel-eslint@8.0.3 and the issue goes away.

Something definitely up with babel-eslint@8.1.2.

[doodlewind]

Possible same issue raised in babel-eslint
babel/babel-eslint#564

[doodlewind]

I investigate a bit and found that a patch for scope analysis is introduced in #542, which is not compatible with babel-eslint@7.x. Since standard@10.x uses babel-eslint@7.x, this patch may introduce unexpected behaviors for standard@10.x.

The good news is that in standard@11.x, dependency version is updated to babel-eslint@8.x. I've tested several permutation and find two workarounds for now:

1. Install standard@10.x with babel-eslint@7.x
2. Install standard@11.x with babel-eslint@8.x

Any ideas fixing standard@10.x with babel-eslint@8.x, or warn user in this case?

[GBarkhatov]

Using babel-eslint@8.0.3 works fine, spend a day solving this.

[pex]

As described in babel/babel-eslint#564 (comment) this issue is not limited to standard but also to XO.

[ematipico]

Thanks @pex for your comment!
Closing the issue as it's not a problem of standard but of babel-eslint@8.1.3. A temporary solution is to downgrade to babel-eslint@8.0.3