-
Notifications
You must be signed in to change notification settings - Fork 12k
NO EFFECT with ng serve --live-reload false #1755
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've confirm this issue exists on 1.0.0-beta.11-webpack as well. |
DAMMAGE |
This flag is not implemented in the webpack version. It should be removed in #1807. |
on version |
If this flag is not implemented, does it mean there is no way to stop the constant unwanted reloading of an app while developing something that involves uploads and downloads? |
For reals? The flag hasn't worked for since August and it still exists in the --help command? At the very least this should be removed. |
Hello, I have the reversed problem, I would like to have live reload working with angular-cli 1.0.0-beta.22-1, but I cannot figure out why it does not work, however it works with lite-server but I would like to be able to start a project with -cli. Maybe have you an idea about what I could check in JSON file or other ? Thanks in advance |
i'm using version 1.0.0-beta.24 and the flag is not working for me also... |
Are there any updates on this? It would be great if we could disable live-reloading. |
angular-cli: 1.0.0-beta.26 it's very important for me to prevent live reloading, but it's not working. |
How do we stop this ? |
I would also like to be able to switch off live-reload and live-recompile ... it get extremely frustrating when I have to make a big change ( possible in multiple files ) and on every save it recompiles the whole project and outputs 19238129038 errors. I want to be able to manually tell it when to recompile and reload all modules. |
@lestard You need to use: ng serve --live-reload=false |
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. |
Thanks!
The text was updated successfully, but these errors were encountered: