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.

Sign up for GitHub

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

Jump to bottom

Why not use the babel-eslint parser? #193

Closed
0x80 opened this issue Jul 17, 2015 · 2 comments · May be fixed by Jankyboy/standard#6, oudomskn/standard#7, I-Cat/standard#14 or Abskpro/standard#3
Closed

Why not use the babel-eslint parser? #193

0x80 opened this issue Jul 17, 2015 · 2 comments · May be fixed by Jankyboy/standard#6, oudomskn/standard#7, I-Cat/standard#14 or Abskpro/standard#3

Comments

@0x80
Copy link

0x80 commented Jul 17, 2015

I am using es7 decorators and noticed that standard linter doesn't allow them, and then found out that standard is not using babel-eslint as it's parser. Please start using that.
@Flet
Copy link
Member

Flet commented Jul 17, 2015

Hello!

Its possible to provide a custom parser to meet these needs:
https://github.com/feross/standard#can-i-use-a-custom-js-parser-for-bleeding-edge-es6-or-es7-support

@0x80
Copy link
Author

0x80 commented Jul 17, 2015

Aha! Thanks. Sorry I missed that.

@0x80 0x80 closed this as completed Jul 17, 2015
@lock lock bot locked as resolved and limited conversation to collaborators May 11, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
The Standard Project
Archived in project
Milestone
No milestone
2 participants
@Flet @0x80