[ng13] ng serve auto compiling infinitely without any changes
See original GitHub issueWhich @angular/* package(s) are the source of the bug?
compiler
Is this a regression?
Yes
Description
Hi, after upgrading ng13 from ng12, I got this issue. It worked well in ng v12.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
No response
Please provide the environment you discovered this bug in
Angular CLI: 13.0.1
Angular Core: 13.0.0
Node: 14.17.3
Anything else?
No response
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:31 (1 by maintainers)
Top Results From Across the Web
angular - ng serve not detecting file changes automatically
Most of the times in Linux, ng serve or ng build --watch doesn't work if the directory doesn't have sufficient permissions.
Read more >Ng Serve: solution keeps on re-compiling - Anthony Marques
Where no changes have been made or saved, but the console keeps on compiling every now and again..it kinda looks something like this....
Read more >ng serve - slow as hell! : r/Angular2 - Reddit
I've just updated my major project to v12 and I'm running ng serve to view css changes but it's taking too long to...
Read more >How to Change Angular CLI ng serve Default Host and Port
Angular CLI will auto-generate all the necessary configuration to build and run your project when it is created. Working with the out-of-the-box configuration ......
Read more >Untitled
Gary's auto parts edmonton, Cold blooded pro easily, Pioneer website singapore, Lejeune base ... Unasyn suspension preparacion, Martor profi no 07100.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Following a debug session with @vincentpalita, we managed to track down what is causing the problem. Will be working on a fix shortly.
Thanks again @vincentpalita for your help.
A remote session would definitly be helpful. I don’t see a way to contact you in your GH profile. Can you please reach out personally on twitter or via email? Thank you.