-
Notifications
You must be signed in to change notification settings - Fork 12k
ng serve live reload takes a long time after initial load #26415
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
i think there has a been a few reports where ng serve is crashing and all you see on the CLI is "reloading clients" have not been able to narrow down exactly why this is happening |
Could this be a duplicate of #26334? Can you try again on 17.0.2 and let us know if it's still an issue for you? |
Apologies for not seeing it's a duplicate. I updated the version now, it does seem to resolve the issue! |
Glad to hear that fixes it. Duplicate of #26334 |
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. |
Which @angular/* package(s) are the source of the bug?
compiler-cli, compiler
Is this a regression?
Yes
Description
I opened a new project with angular 17. When I run 'ng serve', the initial browser load is normal and as I know from previous angular versions. But when I try to live reload after some minor change to my code, the "Reloading client(s)..." takes a long time to execute if successful at all. I had to exit the ng serve and rerun it for it to work again. Here is my bundle size:
Initial Chunk Files | Names | Raw Size
styles.css | styles | 342.01 kB |
polyfills.js | polyfills | 82.71 kB |
main.js | main | 8.73 kB |
Application bundle generation complete. [0.131 seconds]
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run
ng version
)Anything else?
No response
The text was updated successfully, but these errors were encountered: