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
When using a .webp or .gif file that has video / animation frames as an input to the plugin, the output files seem to have stripped those out, and all we're left with are still images.
In my case, my pipeline is something akin to this --- nothing special I think? :
constimage=require('@11ty/eleventy-img')// ...constimagedata=awaitimage(IMAGE_PATH,{widths: [624],outputDir: './_site/i/',urlPath: '/i/',})// `imagedata` is then parsed to the corresponding `picture > source + img` markup.
The text was updated successfully, but these errors were encountered:
I ran into this issue myself and ended up removing animated GIFs from my site for that reason. Curious to see if there's a way to process them while retaining the frames. I know Google provides a gif2webp command-line utility (similar to cwebp) that can be used to convert animated GIFs to animated WebPs. As a temporary workaround, you might be able to process those manually and passthrough-copy them to a dedicated folder for GIFs. Not ideal, though.
When using a
.webp
or.gif
file that has video / animation frames as an input to the plugin, the output files seem to have stripped those out, and all we're left with are still images.In my case, my pipeline is something akin to this --- nothing special I think? :
The text was updated successfully, but these errors were encountered: