-
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
Ctrl + C is not working dev-server with SSR #28336
Comments
Are you using the vite based dev-server with ssr? |
no I am using simple VS Code compiler, and yes SSR is enable. |
I'm not entirely sure what you mean by "VS Code compiler" in this context. You can either be using the Webpack or Vite based dev-server. Given that you're using SSR and encountering this issue, it's probable that you're working with the Vite dev server. This is a known issue in this case, and is appears to be caused //cc @JiaLiPassion |
Encountering the same issue for the past couple of weeks... (Angular 18.2 with Vite/SSR, WSL shell) Reproduction
Workarounds
|
I have the same problem |
same problem here, initially thought taking place only in vs code but however same using external terminal. |
This commit provides a workaround for angular#28336, which occurs due to the interaction between `zone.js` and `listr2`. The issue prevents proper termination of the development server using Ctrl + C when dev-server. Closes: angular#28336
This commit provides a workaround for angular#28336, which occurs due to the interaction between `zone.js` and `listr2`. The issue prevents proper termination of the development server using Ctrl + C when dev-server. Closes: angular#28336
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
Is this a regression?
The previous version in which this bug was not present was
17
Description
The Ctrl+C command is not working to stop the application from the terminal.
Minimal Reproduction
I face this problem after updating angular material : ng update @angular/material
Exception or Error
No response
Your Environment
Anything else relevant?
No response
The text was updated successfully, but these errors were encountered: