You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The output shows in the last line that build/index.html is ignored hwich totally defets the propsuse - beacsue build/index.html was chanegd. And my debug print line at the top show clearly that in _tasks is no ignore attrivute set.
So why is build/index.html ignored and how can I tell livereload to watch all files in the directory build for changes. (The site is not very big; it contains only 114 files).
The text was updated successfully, but these errors were encountered:
As things currently stand, if you make changes "too quickly", they get ignored. I'm personally not 100% sure about how the logic here works, but I'll take a closer look sometime next month.
Sounds like a bit of a straneg logic to me. - Maybe the system is designed to go through the whole motion of notifying the browser and reloading the content for each individual changed file?
Wouldn't it be better to collect all the changes and then do the reloading? Well, - easy for me to critise from the outside. ;-)
I run a livereload server from this code:
When I run this server and then change the stuff in my site directory
build
I get logging output like this:The output shows in the last line that
build/index.html
is ignored hwich totally defets the propsuse - beacsuebuild/index.html
was chanegd. And my debug print line at the top show clearly that in_tasks
is no ignore attrivute set.So why is
build/index.html
ignored and how can I tell livereload to watch all files in the directorybuild
for changes. (The site is not very big; it contains only 114 files).The text was updated successfully, but these errors were encountered: