-
-
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 panics when running with -s exampleSite in v0.123.x #12141
Comments
OK, I have a failing test case for this now and I will fix this. [[module.imports.mounts]]
source = "dist"
target = "static"
[[module.imports.mounts]]
source = "dist/leaflet.scss"
target = "static/leaflet.css" My logic didn't handle the "double mounts" above and paniced when it tried to read the directory as a file. You can workaround this by ... removing the single file mount (and rename or copy the source file). I have reimplemented and simplified the file mounts in Hugo, and I obviously missed some cases where the old code worked, but at least I can now understand my own code :-) But I will fix, thanks for the report. |
Thanks @bep! I agree the “double” mounting is a bit odd. The module is basically wrapping an existing npm package to modularize it for Hugo. I was trying to avoid an additional npm script to rename/copy an existing dist file… |
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. |
What version of Hugo are you using (
hugo version
)?Does this issue reproduce with the latest release?
Yes
Context
When upgrading Hugo from v0.122.0 to v0.123.3 I get a Hugo panic. Below the full error logs (specific to the
mod-leaflet
module):Full logs
To reproduce
git clone https://github.com/gethinode/mod-leaflet.git cd mod-leaflet hugo mod vendor hugo --gc --minify -s exampleSite
Notes
I'm transitioning the various modules maintained by
gethinode
to take advantage of work files (see gethinode/hinode#786), which might prevent this issue. Nevertheless, it seemed to make sense to submit this issue anyways.The text was updated successfully, but these errors were encountered: