-
Notifications
You must be signed in to change notification settings - Fork 12k
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
add option to exit ng serve on error #27309
Comments
I'm a little puzzled about why you're running
Check out the document to see all available options: https://angular.io/cli/serve |
hi @alan-agius4
about our CI setup, we are using nx which has |
update, trying it in a brand new angular 17 application, it does exit |
All Boolean options can be negated using the |
…ommand to exit with -1 if it faced any errors fixes angular/angular-cli#27309
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Command
serve
Description
right now we are facing a big problem in our e2e pipeline because of #27167
it's even worse when it happen with serve than build, because it doesn't exit and the e2e never run and the pipeline stuck for hours till someone notice it and kill it manually or it timeout
it's wasting us a lot of time and resources, at least it should exit when it fails
Describe the solution you'd like
add option similar to
--exit-on-error
or even better a production flag--ci
so that it disable the watch for file changes, make it exit on error and do any needed optimization for this use caseDescribe alternatives you've considered
I can't think of any
if someone has a workaround for this please share
The text was updated successfully, but these errors were encountered: