MikeRogers0 / LivePage

LivePage for Google Chrome reloads website resources (such as CSS, HTML and JavaScript) as they change on the server.

Home Page:https://livepage.mikerogers.io/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Version 2.6.8 not updating cache reliably?

Pseudothink opened this issue · comments

commented

Hi Mike, first--thanks for such a great development tool! I'm just introducing myself to it now, as I'm stepping through Ben Rady's tutorials from his Serverless Single-Page Apps book.

One of the two problems I encountered with LivePage is that it didn't seem to notice when I updated the markup in the index.html file being served to LivePage from my local dev server at http://localhost:9292.

I couldn't figure out why the Jasmine test wasn't passing after the update (as indicated that it should on page 30 of the book), because it was a very simple change that should have worked. After double and triple checking everything, I tried a hard browser cache refresh (Ctrl-F5), and suddenly the Jasmine test showed that it was working fine, as expected. For some reason, LivePage was using the cached version of the file, the whole time.

I'd updated my polling interval to 1000ms, but otherwise I'm using LivePage with its default settings, and I don't think I have any other extensions installed which might be interfering. Any thoughts?

Thanks again, regardless!

Bump. I'm experiencing something similar where small code changes of, say, a line don't trigger a reload whereas larger changes and small changes higher in the .js file trigger a reload. I'm running the build script in this repo and LivePage'ing this .html file locally.