-
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
Angular 13 CLI not stopping after ctrl + c #22216
Comments
This is related/caused by sindresorhus/ora#156 and unfortunately there is no easy way to address this. Note: the build will be cancelled, but it with a delayed. |
Experiencing the same thing with both build and serve. If I try to stop the process with Ctrl + c in |
Same issue here. Sometimes the process doesn't die properly, so builds fail due to an ongoing ngcc process already running. I don't know if this helps but I don't recall this to be an issue in ng12. |
I experienced the same issue with |
Still present with Angular 14 and on Mac |
Not specific to windows. Happens with For a production build the delay can be quite long so this is more than irritating. |
…essed Since version 4, webpack-dev-server by default will shutdown gracefully. This results in `CTRL+C` needed to be pressed multiple times to exit the process. See: https://github.com/webpack/webpack-dev-server/blob/c76b6d11a3821436c5e20207c8a38deb6ab7e33c/lib/Server.js#L1801-L1827 Closes angular#22216
…essed Since version 4, webpack-dev-server by default will shutdown gracefully. This results in `CTRL+C` needed to be pressed multiple times to exit the process. See: https://github.com/webpack/webpack-dev-server/blob/c76b6d11a3821436c5e20207c8a38deb6ab7e33c/lib/Server.js#L1801-L1827 Closes #22216
…essed Since version 4, webpack-dev-server by default will shutdown gracefully. This results in `CTRL+C` needed to be pressed multiple times to exit the process. See: https://github.com/webpack/webpack-dev-server/blob/c76b6d11a3821436c5e20207c8a38deb6ab7e33c/lib/Server.js#L1801-L1827 Closes #22216 (cherry picked from commit 4fcfc37)
…is pressed When using localization we setup `SIGINT` signal to delete the temporary directory. In some cases these resulted in delaying the process from exiting a couple of seconds. Closes angular#22216
…is pressed When using localization we setup `SIGINT` signal to delete the temporary directory. In some cases this resulted in delaying the process from exiting a couple of seconds. Closes angular#22216
… is pressed When using localization we setup `SIGINT` signal to delete the temporary directory. In some cases this resulted in delaying the process from exiting a couple of seconds. Closes angular#22216
… is pressed When using localization we setup `SIGINT` signal to delete the temporary directory. In some cases this resulted in delaying the process from exiting a couple of seconds. Closes #22216
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. |
🐞 Bug report
Command (mark with an
x
)Is this a regression?
Yes, the previous version in which this bug was not present was: v 12Description
With Angular 13 i have on Windows and Mac the Problem that the ng:serve command does not stop after i press ctrl + c.
After i press ctrl+c in the Terminal the Angular CLI still produce cli output.
🔬 Minimal Reproduction
npm start
press ctrl+c or command+c
wait a bit and see the console output in the Terminal.
🔥 Exception or Error
🌍 Your Environment
Anything else relevant?
The text was updated successfully, but these errors were encountered: