Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failing to parse ES7 features, due to espree #426

Closed
andywer opened this issue Feb 18, 2016 · 3 comments

Comments

@andywer
Copy link

commented Feb 18, 2016

Hey there!

I just recognized that standard fails to parse files in which we use class properties like:

class MyComponent extends React.Component {
  static propTypes = {}      # This is were shit hits the fan

  render () {
    return null
  }
}

It fails to parse the file and complains about Unexpected token =. Maybe it would make sense to use babel-eslint?
(See: yannickcr/eslint-plugin-react#43 (comment))

I am a big fan, but not familiar with the inner workings of standard and how it utilizes eslint, though.

@LinusU

This comment has been minimized.

Copy link
Member

commented Feb 18, 2016

@andywer

This comment has been minimized.

Copy link
Author

commented Feb 18, 2016

Ohh sorry, I did not even expect it to be in the Readme. Thank you for the quick response!

@andywer andywer closed this Feb 18, 2016

@LinusU

This comment has been minimized.

Copy link
Member

commented Feb 18, 2016

No problem 👌

@lock lock bot locked as resolved and limited conversation to collaborators May 10, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
2 participants
You can’t perform that action at this time.