Standard considers static class properties as parsing error in version 12

[Visya]

What version of standard?
standard@12.0.1

What operating system, Node.js, and npm version?
MacOS, Node.js v8.12.0, npm 6.4.1

What did you expect to happen?
Standard allows static properties in classes

What actually happened?

class HomeScreen extends React.Component {
  static navigationOptions = {
    title: "MyApp"
  }
  ...

Standard output:

../screens/Home.js:7:28: Parsing error: Unexpected token =

[xiaweiss]

ES7 is not supported.
Same problem:

class Foo {
    myFunction  = () => {
  
   }
}

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[brodybits]

??

[xiaweiss]

the above code will report lint error.
but in standard version 10.0.3, it worked, no error

[xiaweiss]

it also might be a bug of package linter-js-standard of atom editor

[lovetingyuan]

same problem, anyone will fix it?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[brodybits]

?

[feross]

Hi everyone,

You need to npm install babel-eslint and tell standard to use it as the parser. See: https://standardjs.com/#how-do-i-use-experimental-javascript-es-next-features

Once this is a Stage 4 language proposal and ESLint adds support for it, then the babel parser will no longer be required.