Skip to content
This repository has been archived by the owner on May 6, 2020. It is now read-only.

Ability to configure asset paths #1

Closed
jewbetcha opened this issue May 10, 2017 · 2 comments
Closed

Ability to configure asset paths #1

jewbetcha opened this issue May 10, 2017 · 2 comments

Comments

@jewbetcha
Copy link

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!

@vseventer
Copy link
Owner

The problem is that Hugo copies everything in static/ to the destination folder, while the point of this plugin is to have Webpack process the images, and then copy the resulting files to the destination folder. Using static/ wont work, hence this plugin uses a different folder, static-src/. I could make this folder configurable, just want to make sure that would fix your issue.

@jewbetcha
Copy link
Author

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.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants