lektor live server not pushing the changes to the browser

57 views Asked by At

Many other testing http server like some available for VScode, Atom, Hugo etcetera are "live" server. I mean that as soon as I save a file the change appears in the browser.

With Lektor I have to make my changes (say some content, or the css) then go to the browser window and refresh the page. Actually when I change anything (just typing, without even saving!) I see that the involved pages are regenerated (pruned), but the changes are not pushed to the browser (lektor 3.2.0 + firefox on win10 in my case).

Am I missing some configuration? On the browser side eventually?

Thank you

1

There are 1 answers

0
lupdidup On

Lektor does not support hot-reloading as already said in the comments. And to clarify your statement, you said Lektor does reload pages after you type something, even before it is saved. That is not correct, or at least a coincidence. Yes, Lektor does indeed sometimes prune without you changing a file. But it was (most likely) not triggered by your typing. Lektor only re-generates affected files after you save a file.