-
Notifications
You must be signed in to change notification settings - Fork 12k
ng serve doesn't load or reload the page when Chrome DevTools are open #5134
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
Possibly related to #5117 |
I believe this may be fixed by a pending PR: #5164 |
Just noticed that the problem persists even after running ng build --prod and publishing to staging server. The application works as expected when closing the DevTools. Edit: Oh my god... I disabled javascript in DevTools for testing a couple of days ago. No wonder the Angular app wasn't working. This is embarrassing. |
Easy thing to forget you changed! Better close the issue. |
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. |
OS?
macOS Sierra 10.12.3 (16D32)
Versions.
@angular/cli: 1.0.0-rc.0
node: 6.10.0
os: darwin x64
@angular/common: 2.4.8
@angular/compiler: 2.4.8
@angular/core: 2.4.8
@angular/forms: 2.4.8
@angular/http: 2.4.8
@angular/platform-browser: 2.4.8
@angular/platform-browser-dynamic: 2.4.8
@angular/router: 3.4.8
@angular/cli: 1.0.0-rc.0
@angular/compiler-cli: 2.4.8
Repro steps.
If i manually reload http://localhost:4200 with DevTools open in Google Chrome 56.0.2924.87 (64-bit) it loads the html-file but nothing more. The only request listed in the network pane is the initial html-file request. The file watch feature also stops working. If I close the DevTools it works as expected. Also works in latest Firefox and Safari.
Worked until recently. My guess is that it happened when i updated npm packages. angular-cli 1.0.0-beta.30 -> 1.0.0-rc.0. Doesn't work when I reset to 1.0.0-beta.30.
Edit: Also tested with a new project and disabled all Chrome extensions. Same problem.
How to reproduce:
ng new lol
cd lol
ng serve
The log given by the failure.
No error in the console or terminal.
The text was updated successfully, but these errors were encountered: