[BUG] Fix duplicate target paths for icons and headers

[markdumay]

Describe the bug

Hinode generates several assets twice, resulting in duplicate target paths. This applies to icons and possibly server headers too.

To reproduce

Add the --printPathWarnings to the Hinode server command. For example:

hugo server --bind=0.0.0.0 --disableFastRender --printI18nWarnings --printPathWarnings

Expected behavior

Assets should be generated only once.

Log file

Hugo generates the following log:

WARN  Duplicate target paths: /icons/accordion-button-active-icon-dark.svg (2), /icons/accordion-button-active-icon.svg (2), /icons/accordion-button-icon-dark.svg (2), /icons/accordion-button-icon.svg (2), /icons/btn-close-bg.svg (2), /icons/btn-toggle-dark.svg (2), /icons/btn-toggle.svg (2), /icons/carousel-control-next-icon-bg.svg (2), /icons/carousel-control-prev-icon-bg.svg (2), /icons/form-check-input-checked-bg-image.svg (2), /icons/form-check-input-indeterminate-bg-image.svg (2), /icons/form-check-radio-checked-bg-image.svg (2), /icons/form-feedback-icon-invalid.svg (2), /icons/form-feedback-icon-valid.svg (2), /icons/form-select-indicator-dark.svg (2), /icons/form-select-indicator.svg (2), /icons/form-switch-bg-image-dark.svg (2), /icons/form-switch-bg-image.svg (2), /icons/form-switch-checked-bg-image.svg (2), /icons/form-switch-focus-bg-image.svg (2), /icons/navbar-dark-toggler-icon-bg.svg (2), /icons/navbar-light-toggler-icon-bg.svg (2), /icons/search.svg (2)

Host environment

Please complete the following information where applicable.

• Hinode version: [v1.6.3]

Hugo environment

Copy the output of hugo env or npm run env here.

hugo v0.147.9-29bdbde19c288d190e889294a862103c6efb70bf+extended darwin/arm64 BuildDate=2025-06-23T08:22:20Z VendorInfo=gohugoio
GOOS="darwin"
GOARCH="arm64"
GOVERSION="go1.24.0"
github.com/sass/libsass="3.6.6"
github.com/webmproject/libwebp="v1.3.2"
github.com/sass/dart-sass/protocol="3.2.0"
github.com/sass/dart-sass/compiler="1.89.2"
github.com/sass/dart-sass/implementation="1.89.2"

[markdumay]

This issues is still present in Hinode v2.2.8.