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'm using NuxtPicture with format="avif,webp" and ipx. When I test the page in npm run dev, the image type in Network tab is correct: image/avif. However, when I run npm run generate and serve the build, the images in Network tab have the content type image/webp which is the original content type of my source image.
I see the image is served from a correct avif folder: GET /_ipx/w_400&f_avif/images/blog/1-front-panels-tips/01-front-matter.webp
@danielroe Am I correct thinking that for nuxt generate, we cannot distinguish what kind of format extension does the browser provide (the most performant one) so we use webp by default?
And this format fallback would only work fully on SSR apps?
I'm using
NuxtPicture
withformat="avif,webp"
andipx
. When I test the page innpm run dev
, the image type in Network tab is correct:image/avif
. However, when I runnpm run generate
and serve the build, the images in Network tab have the content typeimage/webp
which is the original content type of my source image.I see the image is served from a correct
avif
folder:GET /_ipx/w_400&f_avif/images/blog/1-front-panels-tips/01-front-matter.webp
I tried putting this in my nuxt config:
but the content type after
generate
is stillimage/webp
.I'm using
@nuxt/[email protected]
Originally posted by @arxwtf in #1345 (comment)
The text was updated successfully, but these errors were encountered: