Image Quality on per image base about next-image-export-optimizer

[Niels-IO]

Hi @Fritze1602

Thanks for the explanation! I understand your point.
I will put this feature on the backburner. Maybe I have a better idea on how to do it in the future.

Cheers
Niels

[Niels-IO]

Hi @Fritze1602

Thank you very much for your kind words.
It wouldn't be possible to pass the quality as a prop as the module does not look at the code base. It only takes the images from the image folder and uses them to do the image resizing operation.

The only way that I could think this would be possible, if the hash file stores the requested quality as an argument per image. At first this would be the default and then you could change it here.

I don't think this would be a particular elegant solution though.

Can I ask why you want to steer the quality prop on a per image basis?

[Fritze1602]

Hi. Thanks a million for your kind reply.
Ohoh. That doesn't sound like an easy solution or a quick win. I like this feature (next/image) for projects with completely different images/qualities (inputs). I have found these "deliveries" often on architecture projects. Some images with same dimensions 1,5MB others 0,4MB. So the per image solution becomes very handy to avoid a whole step of image/pre-processing. This can be done on the fly or via CMS..
So I have created my component library that makes heavy use of the Next/Image Quality feature, and I want to use it in static export projects with your amazing library as well.
Sorry for my English btw. I hope my "suggestion" and the idea became clear anyways.

[Fritze1602]

Thanks a million for this and your thoughts about it. I hope I will increase my abilities in next js and your fantastic library in the nearer future, so I hopefully come up with a few ideas too. At the moment I am simply not good enough... .