You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not really familiar with how the manifest feature works, but I would assume this is not a bug rather it is expected.
The Vite plugin emits resized variants of the original image, but the original image itself is not used anymore for the build output. That's why I think it is expected that the manifest will not refer to the original file (resources/img/index/kontakt.jpg) anymore.
Two questions related to that...
why do you need those images in the manifest? The images will be referred to in some of the JS chunks. There is no need to have anything in your index.html point to them directly. I assume the manifest is used to construct the HTML in some customized way, is that right?
Have you enabled the vite plugin for all image imports? The docs recommend keeping default asset imports untouched, so the vite built-in asset handling continues to work for them, and have a query param like ?responsive to opt into the specials handling of this plugin where needed. That way if you want to get the URL of the original images, that would still work, and I think that should also keep those references in the manifest in place.
Hey,
first thanks for your great work! I just tried responsive-image with vite 5 and 6 and noticed one issue:
If i glob import an image without responsive-image, its included in manifest.json like this:
if u use responsive-image, its included without path:
This causes inconsistent manifest.json paths. Is this a bug or if not, how can i fix it?
Thanks!
The text was updated successfully, but these errors were encountered: