ChatGPT解决这个技术问题 Extra ChatGPT

Angular cli - how to disable auto reload when ng serve

When serving my app with the Angular cli, how do I disable auto-reload?

ng --help mentions the --live-reload option, but I can't make it work.

ng serve --live-reload=false or ng serve --live-reload false do not work

EDIT : it seems to be a bug https://github.com/angular/angular-cli/issues/1755

we, poor windows devs, need this to prevent search indexer / antivirus stuff to trigger permanent rebuilds... Did you find any solution ?
according to this pull request it should be fixed soon

B
BrunoJCM

Just do ng serve --live-reload false or ng serve --no-live-reload

It used to not work, this PR solved it.


Can I stop reloading on some particular files like I want to stop reloading on changes in css files, is it possible ?
for me i had to add an equals sign ng serve --live-reload=false
not working for me with --aot --prod. haven't tried other settings, but this isn't working.
why would develop with --prod mode on, though?
@maxbellec because development includes end to end testing. I might use it 2% of the time but I still want the option to test all my production config - and any nuances of production builds. Since I can now use argo tunnel through cloudflare (which caches) to reverse proxy to my machine I can get a pretty good idea how fast the site will be on a cell data connection without needing a real staging environment.
s
s sharif

serve your application with this command:

ng serve --live-reload=false

if you want to run your application in prod mode, use following command

ng serve --source-map=false --aot --prod --live-reload=false

P
Pedro Lopez

I think you only want to disable the rebuild on change option

Just try:

$ ng serve --watch=true|false

--watch is one thing, --live-reload is another. I don't think your answer really address the OP.
Yet this is the command that made my CPU usage associated to the angular process go down from 50 to 0%
z
zmanc

The solution for this is to upgrade the version of the CLI you are using. The CLI now uses in memory for the build process and is no longer writing to disk. This helps with the antivirus/disk write issue.


it might fix the problem from the first comment, but I believe it does not solve the real problem, there is still (to my knowledge, last time I checked in the Github discussions) no way to make --live-reload work with the cli
live-reload disable is coming back, but I guess the other question is why is this a need? I have not seen a use case for disabling it.
it mostly annoys me when I'm editing a template, then I come back to the browser the check something in the dev tools only to find out the page I'm working on is not available since the app is broken (it refreshed before I finished editing the template) and I can't see the page anymore
seeing the number of comment on the github issue, I guess I'm not the only one being annoyed by this
Still hitting this. I'm trying to run ng serve via cloudflare (they have a new tunnel called argo tunnel that allows me to reverse proxy from my dev machine). I want to test on proper https, on a CDN without a proper build. Also sometimes I may be editing realtime with others previewing the site in a meeting and I don't want it reloading until I tell them to hit reload.