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

Better output when parser fails #32

Closed
oliverwoodings opened this issue Nov 20, 2016 · 3 comments
Closed

Better output when parser fails #32

oliverwoodings opened this issue Nov 20, 2016 · 3 comments

Comments

@oliverwoodings
Copy link

Right now if you have a syntax error, babylon fails but doesn't actually tell you where the issue is - the stack trace just points to babylon itself:

screen shot 2016-11-20 at 19 35 40

Is there any way to get better output from this, or am I missing something?

@leebyron
Copy link
Owner

I think babylon might have improved their errors in a more recent version - I'll take a look

@leebyron
Copy link
Owner

Indeed, updating to latest babylon highlights the line with the issue which is much nicer. I just updated the dependencies to pull it in

@oliverwoodings
Copy link
Author

You're on 🔥! Thanks again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants