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
Recover from "missing semicolon" errors #12437
Recover from "missing semicolon" errors #12437
Conversation
Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/39074/ |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit cf0aef0:
|
Can you rebase on #12375 ? So we are confident that it also works when |
70ad6f1
to
c7d1b7e
Compare
...r/test/fixtures/es2017/async-functions/invalid-escape-export-dflt-async-function/output.json
Outdated
Show resolved
Hide resolved
...l-parser/test/fixtures/es2017/async-functions/invalid-escape-sequence-function-list/input.js
Outdated
Show resolved
Hide resolved
44ac956
to
cf0aef0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💯
The original motivation for this PR was to prevent throwing in #12436, but then I realized that this is an error that it's really easy to recover from.
Unexpected token, expected \";\"
and now they throw a similarly unuseful error (adding;
was not the necessary fix in these fixtures).