-
-
Notifications
You must be signed in to change notification settings - Fork 200
Multiple images with same name #246
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
Comments
Hey @graille, That's indeed an issue due to the way the manifest.json file works. We already discussed about that kind of thing before due to another issue that was a bit worse since the files would use the same name (no hash) and would end up overwriting each other:
TL;DR:
I'm still not sure about what we should do about that (ping @weaverryan) but in the meantime if you want to keep the same tree you can force the use of the Encore.configureFilenames({
images: '[path][name].[hash:8].[ext]',
fonts: '[path][name].[hash:8].[ext]'
}); |
Still open :( |
Hi @Kocal. AFAIR it does not. |
Hi,
I've found an issue with Encore's image management when files have the same name
My
assets/images
folder loke like this :In my app.js, I call each static images used by my project (in JS or CSS files) one by one (@images is a webpack alias):
(The problem is the same if files are referenced in a CSS file and not in a JS file)
But at the end, each images are moved in
public/build/images
directory :But the manifest.json does not reference the two images :
Idea :
Would it not be better to have the same file tree in the
public/build/images
directory ? Something like this :The text was updated successfully, but these errors were encountered: