-
Notifications
You must be signed in to change notification settings - Fork 130
compiler errors kill gulp-watch #585
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
Comments
+1 |
Catching build errors to prevent the gulp watch process from crashing is covered in the "Reporters" section of the documentation. If you add |
+1, version 4.0.2 has a stable version if anyone needs a quick fix. |
This is an effect of #295. We now crash on compiler errors, which is especially desired in a CI context. However, for a watch build, you don't want to crash. When you install gulp 4, gulp will catch the error for you and continue working. The solution by Sam is a good option if you cannot upgrade to Gulp 4 yet. I'll keep this issue open, as you shouldn't get a |
can't post details, but typescript compiler errors cause gulp-watch to stop responding to file changes.
all packages are up-to-date.
the compiler errors, which are expected, are followed by this (new) suspicious text:
The text was updated successfully, but these errors were encountered: