Setting placeholder from "empty" to lowest possible image size of optimised images about next-image-export-optimizer HOT 5 CLOSED

Hi @Perni1984,
I just finished the merge in PR #13 and published a new version. There was no particular reason for the delay 🙂
If you like, you can test the new release and let me know if everything works as expected.

from next-image-export-optimizer.

Hi @ueberf,

Awesome suggestion! I coded it up, and you can have a look at the code in the PR #13.

Do you have a recommendation about the width we should choose for the blur image? I think the images with 32px width would maybe look better than the ones with 16px width and still be sufficiently small?

Cheers
Niels

from next-image-export-optimizer.

Just to comment on this, I know I'm not involved but the docs say 'less than a 10x10' is ideal, because its enlarged. Check it out - https://nextjs.org/docs/api-reference/next/image#blurdataurl

Including larger images as placeholders may harm your application performance

from next-image-export-optimizer.

Hi @lgn-lvx3,

Thanks for the hint! I think they would know best, so I adapted the Pull Request #13 to have a dedicated config variable for automatic generated blur images. When the variable generateAndUseBlurImages is true, it generates an additional image with a width of 10px and uses it in the ExportedImage component.

from next-image-export-optimizer.

Hey @Niels-IO we think this is a great addition to your package, is there any reason you did not merge it yet? And if so, can we support on getting any eventual blockers out of the way?

from next-image-export-optimizer.