-
Notifications
You must be signed in to change notification settings - Fork 71
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
abortOnError
enhancement: get *all* errors, *then* abort
#168
Comments
Yep. Might get messy due to the way rollup detects failure (see continueAfterFirstError branch if you want to test it out). |
Thank you! I'll give it a try hopefully later today and let you know how it works for me. Out of curiousity: I saw you also added an additional flag abortOnWarning, what kind of warnings would it abort on in this case? |
It seems to work first test. I'd like to test a bit more coming days if you're not in a rush with it? |
Sure, no rush, I'm yet to do a proper testing on it myself. |
abortOnError
enhancement request: get *all* errors, *then* abort
abortOnError
enhancement request: get *all* errors, *then* abortabortOnError
enhancement: get *all* errors, *then* abort
Hello there,
Currently the option
abortOnError: true
aborts on the first error it encounters when checking a typescript file. When set to false it doesn't bail out at all (and often succeeds completely, even though typescript reported several semantic errors in multiple files e.g.).I'd like an in-between option, that checks all typescript files, gathers the errors reported, and if there is any error at all (or more) spits it all out at once at the end - and aborts.
Currently the abortOnError: true is painful to work with with (many) errors in large projects, and not aborting at all, is just wrong here as the resulting rollup bundle will be broken.
Would something like this be possible? Thank you.
The text was updated successfully, but these errors were encountered: