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

Fault-tolerant @bable/parser parsing #10316

Closed
m4nuC opened this issue Aug 11, 2019 · 2 comments · Fixed by #10363
Closed

Fault-tolerant @bable/parser parsing #10316

m4nuC opened this issue Aug 11, 2019 · 2 comments · Fixed by #10363
Labels
i: enhancement outdated A closed issue/PR that is archived due to age. Recommended to make a new issue

Comments

@m4nuC
Copy link

m4nuC commented Aug 11, 2019

Fault-tolerant flag option for parsing

Is your feature request related to a problem? Please describe.
acorn-loose is a thing, and esprima can be passed a tolerant flag with a value of true. For my usecase, it would be beneficial to reproduce this with babel parser.

Describe the solution you'd like
A flag option to be passed to the parser API

@babel-bot
Copy link
Collaborator

Hey @m4nuC! We really appreciate you taking the time to report an issue. The collaborators on this project attempt to help as many people as possible, but we're a limited number of volunteers, so it's possible this won't be addressed swiftly.

If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack community that typically always has someone willing to help. You can sign-up here for an invite.

@JLHwung
Copy link
Contributor

JLHwung commented Aug 23, 2019

#10363 is related to this request.

@lock lock bot added the outdated A closed issue/PR that is archived due to age. Recommended to make a new issue label Feb 4, 2020
@lock lock bot locked as resolved and limited conversation to collaborators Feb 4, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
i: enhancement outdated A closed issue/PR that is archived due to age. Recommended to make a new issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants