This repository has been archived by the owner on May 6, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6
Ability to configure asset paths #1
Comments
The problem is that Hugo copies everything in |
Ahh sure, I see. We already have all other asset processing in Webpack configured, so I might try to just mimic your method of processing images and then copying over. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I really want to use this, because I've been looking for a way for Webpack to know about images in my HTML templates for my Hugo site. However it would be great if this plugin wasn't so opinionated about where things are/should be stored. We have a custom theme we've developed and reuse, and all assets are in
static/
, in which Webpack is already building/compiling.Are there any plans to have the ability to configure where
hugo-webpack
looks for assets? Or the ability to specify a custom theme?Thank you!
The text was updated successfully, but these errors were encountered: