-
Notifications
You must be signed in to change notification settings - Fork 12k
feat(angular_devkit): stop blocking karma after compilation error #11181
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
Conversation
LGTM, thanks for improving this! By the way, have you found a way to exit karma gracefully in a programmatic way? I haven't really found one that doesn't call |
No, that isn't possible (that I know of). The only way documented way to stop karma is using The callback parameter defaults to In most cases (stryker, ng test, ...) the process hosting the karma server is also the process that would be sending the stop command, so the callback isn't even executed in those cases, as Karma deserves some more love from the open source community. Unfortunately, I don't have the time for it. Btw, when is the next release of the Angular CLI? I can't wait to try it out with Stryker. |
Yeah that's the conclusion I got to as well, just wanted the double check if I was missing anything. Next release of the CLI and devkit packages should be next week. |
I see there is a new release: However, the new code seems to be absent @filipesilva Did something go wrong during release? |
I see. It is released under the |
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. |
This PR removes the blocking of karma in case of compilation errors. This will not influence regular developer workflows (with
ng test
andng test --single-run
), but does help plugin creators relying onkarma run
functionality (withsingleRun: false
andwatch: false
).Fixes #11170