browser-sync does not refresh browser
See original GitHub issueWhere to find the issue
cwa-website
Describe the issue
This is a testing issue only. It does not affect the production website.
When making source changes to cwa-website, browser-sync
announces “Reloading Browsers”, however it does not refresh the browser contents as it should.
Steps to reproduce
Execute
npm start
Terminal shows
[Browsersync] Serving files from: ./public
Finished 'server' after xx ms
Starting 'watch'...
Finished 'watch' after xx ms
Finished 'start-server' after xxx ms
Finished 'default' after xx s
Web browser displays http://localhost:8000/en/
Open src/data/index.json
in an editor.
Make a change, such as changing the title in line 5 and save the change.
Starting 'resetPages'...
Finished 'resetPages' after xx ms
Finished 'pages' after x.x s
[Browsersync] Reloading Browsers...
Note that browser contents have not changed.
Press F5
(refresh) in browser
Now the changes which were made are displayed.
Expectation
When browser-sync displays “Reloading Browsers…” then the contents of the browser should be refreshed.
This is documented in README - Start server as:
“The web server uses public as its base directory. It also watches for file changes and refreshes the browser contents if necessary.”
It is also a documented function of Browsersync.
Synchronized scrolling between multiple browsers also does not work for cwa-website as documented in the Browsersync documentation.
Workaround
To refresh the page after making a change to the source, press F5
(refresh) in the browser window.
If there is no solution to this issue, then this hint should be added to the README - Start server section.
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (7 by maintainers)
Top GitHub Comments
@MikeMcC399 Thanks for the wishes! Hope you had/are having also some nice happy Christmas time!
Thanks for the PR!
I am trying to find out the reason for this not working, but I don’t know if I will get to the bottom of it.
It works with a simple test page, so there is something about the complexity of the cwa-website which is causing a problem.