-
-
Notifications
You must be signed in to change notification settings - Fork 7.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hugo server - Race conditon/timing issue when using generated css in html #12532
Comments
Please edit your description to make it legible. When posting code, configuration, or data, please wrap the text within backticks or use the
|
Sorry, pasted it and the backticks were not kept |
Out of curiosity, what happens if you disable PostCSS when running in development mode? |
So, i did some testing, and removing the postCSS pipe/transform dident do anythng. However, removing "| fingerprint" DOES fix it. So: |
What version of Hugo are you using (
0.126.1
)?Does this issue reproduce with the latest release?
Yes
Setup
Hugo 1.125/126
PostCss
Node 22
Issue
When using hugo pipes to process/generate a css file, and then using the css file in the html, since 0.125+ hugo tries to render the html pages before the css has ben processed, causing any change in a file detected by livereload to cause hugo server to fail, needing to be manually restarted.
This is due to the resource trying to be accessed not yet existing with message
Hugo server is ran like:
Restarting hugo server fixes it, and its only when livereload triggers a refresh.
Example:
htmlfile.html
Inlining the css in the same file:
Fix
I havent had time to look trough the code but the issue started from 0.125+ and is only appearing when running hugo server and is consistently happening on every change livereload detects. Does disablefastrendersomehow not cause a full reload?
The text was updated successfully, but these errors were encountered: