Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upFailing to parse ES7 features, due to espree #426
Comments
This comment has been minimized.
This comment has been minimized.
|
This is covered in the documentation: Can I use a custom JS parser for bleeding-edge ES6 or ES7 support? |
This comment has been minimized.
This comment has been minimized.
|
Ohh sorry, I did not even expect it to be in the Readme. Thank you for the quick response! |
andywer
closed this
Feb 18, 2016
This comment has been minimized.
This comment has been minimized.
|
No problem |
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.
andywer commentedFeb 18, 2016
Hey there!
I just recognized that standard fails to parse files in which we use class properties like:
It fails to parse the file and complains about
Unexpected token =. Maybe it would make sense to usebabel-eslint?(See: yannickcr/eslint-plugin-react#43 (comment))
I am a big fan, but not familiar with the inner workings of
standardand how it utilizes eslint, though.