LiveReload doesn't work with --disableFastRender option.

[nureon22]

I'm running development server with --disableFastRender option. My project contains SCSS files and I use dart sass to compile to CSS. When I make changes to my SCSS files, live reload doesn't happen. I also tried changes in HTML layout files but nothing reflect in browser. I also test on both latest Firefox and Chromium browsers. I built Hugo from source using go1.22.1 on Debian bookworm.

What version of Hugo are you using (hugo version)?

$ hugo version
hugo v0.131.0+extended linux/amd64 BuildDate=unknown

Does this issue reproduce with the latest release?

Yes, I'm using latest release.

[bep]

There should be very few situations in the current Hugo (this was not the situation some time ago) where --disableFastRender will somehow improve things, so I suggest you just drop that flag for now.

[nureon22]

--disableFastRender flag is very useful for me. Without this flag, when I change draft value in Markdown's front matter, Hugo doesn't regenerate HTML pages sometime. I'll be waiting for improvements in next releases. When it comes to static generator, Hugo is my favorite one 🥰.

[adrian5]

I have this issue on v132 without --disableFastRender (Firefox). It didn't occur for me in v129, which I used until recently. Should I open a new issue Bjørn?

Edit: LiveReload appears to work with CSS, but not SCSS.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help. If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open. If this is a feature request, and you feel that it is still relevant and valuable, please tell us why. This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.