Babel-eslint: Broken lint on class property transform after upgrading to v8.1.2

[doodlewind]

Hi, this underlying library is awesome and fundamental, thanks!

I was using [email protected] together with latest standard and babel-presets-stage-0. With this config, following code snippet works fine:

class Foo {
  bar = null
  baz = () => true
}

In VSCode, this.bar can also be added to automatic completion list. Running standard from command line yields no error.

After upgrading this library to v8.1.2, standard complains:

standard: Use JavaScript Standard Style (https://standardjs.com)
  /Users/ewind/code/playground/src/index.js:2:3: 'bar' is not defined.
  /Users/ewind/code/playground/src/index.js:3:3: 'baz' is not defined.

Neither can VSCode "sense" this.bar then. Am I missing some extra configuration?

[Skylsmoi]

I have the same issue, using standard loader too.

I can add that after testing every versions of babel-eslint, the issue starts at version 8.1.0

[doodlewind]

I investigate a bit and found that a patch for scope analysis is introduced in #542, which is not compatible with [email protected]. Since [email protected] uses [email protected], this patch may introduce unexpected behaviors for [email protected].

The good news is that in [email protected], dependency version is updated to [email protected]. I've tested several permutation and find two workarounds for now:

1. Install [email protected] with [email protected]
2. Install [email protected] with [email protected]

See also https://github.com/standard/standard/issues/1035

Guess this is not an issue about babel-eslint, closing for now.

[pex]

Unfortunately I am having the exact same issue using XO and babel-eslint version 8.1.2. Here's a repo reproducing the case: https://github.com/pex/xo-babel-eslint-class-properties

Everything works fine using babel-eslint version 8.0.3.

[RKushnir]

@doodlewind @ematipico

Guess this is not an issue about babel-eslint, closing for now.

Closing the issue as it's not a problem of standard but of [email protected] (https://github.com/standard/standard/issues/1035)

Please, leave at least one of the issues open, so it doesn't get lost.

[RKushnir]

Looks like the issue has been resolved. Works for me on 8.2.1 with the standard 11.0.0.