-
Notifications
You must be signed in to change notification settings - Fork 12k
ng serve not detecting file changes #26325
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
Can you please provide the output of |
Angular CLI: 17.0.0
Node: 20.9.0
Package Manager: npm 10.1.0
OS: win32 x64
Angular:
...
Package Version
------------------------------------------------------
@angular-devkit/architect 0.1700.0 (cli-only)
@angular-devkit/core 17.0.0 (cli-only)
@angular-devkit/schematics 17.0.0 (cli-only)
@schematics/angular 17.0.0 (cli-only)
Ruslan Katz
пт, 10 нояб. 2023 г. в 16:46, Alan Agius ***@***.***>:
… Can you please provide the output of ng version
—
Reply to this email directly, view it on GitHub
<#26325 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJRSPWW7INZO7BFLA2IMFUTYDY425AVCNFSM6AAAAAA7GIYNAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBVHA3TGNZQHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
The dev server isn't picking up changes to ts, html and scss at all.
Do you have some solution?
Ruslan Katz
пт, 10 нояб. 2023 г. в 17:38, Michael Guay ***@***.***>:
… We're also seeing this from migrating to
@angular-devkit/build-angular:application.
Interestingly the dev server is picking up changes to ts and scss but
completely ignores html.
—
Reply to this email directly, view it on GitHub
<#26325 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJRSPWS3TKZQGEU5ZBMR3ZTYDZC6RAVCNFSM6AAAAAA7GIYNAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBVHE2TOMZWHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
cannot confirm 100%. watch and reload works for me on apple silicon with node 20.9 and [email protected], BUT it seems not to recover from broken scss (angular-sass) code ![]() ![]() does not recover from error after fix and save for (s)css filesbroke scss, saved, fixed, saved,... will not recover from error ![]() |
I am also facing the same issue, it sometimes work and sometimes it doesn't. Most of the times it detect changes a few times and then suddenly stops deteting the changes. |
This is exactly what I'm experiencing as well. Changes to |
Confirm the same issue |
In my case, a similar problem began to occur after migrating to application builder (it was fine while using webpack). It turned out that the server did not detect file changes when the source directory name started with a dot (.). Changing the folder name so that it does not start with a dot solved the problem for me |
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?
Don't known / other
Is this a regression?
Yes
Description
Generate a brand new project ng new project
Select scss and all other defaults
run npm start
any changes 4.a change *.ts 4.b change *.html 4.c change *.css
save file
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 (run
ng version
)No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: