-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Unterminated regular expression literal when using division #18607
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
Labels
Duplicate
An existing issue was already created
Comments
Seems to be working with the latest which would make sense since @sandersn and @weswigham have been working on arrow function lookahead stuff. Can you give our nightlies a try?
Edit: realized you may not be using this with npm 😄 |
Let's add a test case here. |
@DanielRosenwasser Seems plausible. Works with latest for me. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Uh oh!
There was an error while loading. Please reload this page.
TypeScript Version: 2.5.2 (works in 2.3.4) - try it in the Playground.
Code
The below is a repro as minimal as I could make it. Changing almost anything will fix the parse errors.
Expected behavior:
No parser errors.
Actual behavior:
Several errors starting with "= expected" and "Unterminated regular expression literal".
The text was updated successfully, but these errors were encountered: