-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
Struggling to get an emit failure with 1.5 #2290
Comments
Previously we blocked emit in the face of early errors. it was getting a bit arbitrary what is early and what is not, in #1527 we have relaxed this restriction, and now we emit even with errors. |
So with |
For JavaScript/source maps yes. we will always emit. for declarations, we currently have a check on errors. we are still talking about this part, whether to block declaration emit on errors (current behavior) or enable it as well. |
Thank you. That answers all my queries ❤️ |
Previously the following would fail to emit due to parsing errors:
Now it does emit JS:
What's more is that something crazy like:
does an js emit:
Are you guys aware of anything that will block an emit now? I just want this for a test ❤️
refs : TypeStrong/atom-typescript#179
The text was updated successfully, but these errors were encountered: