Skip to content

Site is not auto reloading if "ng serve" is running. #6561

Closed

Description

@DurgaAbhist

Hi Sir, Madam,

I'm Durga Abhist and I recently started working with Angular/CLI tool, I'm facing a problem while executing the file, that is when I run "ng serve " command then this command helps us in auto reloading the site when any changes are made in the source file but in my system it is not happening (i.e. site is not auto reloading and when I forcely reload the site then also it is not getting updated as per changes made in the source file).

The site is getting updated only when I terminate the "ng serve" command and again run the same command("ng serve") then only my site is getting updated.

So it becomes hard for me to terminate the server and connect the server, when ever the changes are made, so I request you Sir/Madam help me out in this issue.

Activity

  1. filipesilva commented on Jun 6, 2017

    @filipesilva
    Contributor

    Heya, there are a few reports of live reloading not working properly but they are heavily dependent on the system and setup. My advice is to have a look at the existing issue on this topic (#1610), perhaps some of the fixes suggested there apply to your case.

  2. kartikchauhan commented on Mar 24, 2018

    @kartikchauhan

    Restarting my system helped in fixing the issue.

  3. simeyla commented on May 10, 2018

    @simeyla

    Doesn't seem like it's related to auto reloading because you say

    when I forcely reload the site then also it is not getting update

    I just had the same problem:

    • I am using a ASPNET Core application with a development proxy to pass through to port 4200
    • I noticed that when accessing http://localhost:4200 directly in the browser (bypassing the proxy) then the reloading logic worked just fine
    • So I assumed it was something in the proxy caching it, but restarting the ASPNET Core server did nothing
    • Then I remembered I'd been playing with benchmarking and using --aot command which builds into the dist folder
    • I deleted the contents of ClientBin\dist and re-ran my npm start command (which runs ng serve) and then everything was back to normal again :-)

    Still not clear on the exact rules at plan here - but deleting delete ClientBin\dist can't do any harm.

  4. angular-automatic-lock-bot commented on Sep 8, 2019

    @angular-automatic-lock-bot

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    This action has been performed automatically by a bot.

  5. locked and limited conversation to collaborators on Sep 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions