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
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.
The text was updated successfully, but these errors were encountered:
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.
--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 🥰.
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.
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
)?Does this issue reproduce with the latest release?
Yes, I'm using latest release.
The text was updated successfully, but these errors were encountered: