Hmm not sure if this is needed it's already supported: #42 (comment)

Edit: unless the intention is to set a default fetchpriority other than auto?

I'll just say as a consumer of the APIs provided to us by the browser gods, I have seen a lot of benefit manually specifying fetchpriority. When compared to decoding which is already implemented, I have never seen decoding make a noticeable difference in scores or objectively. I have opened another issue questioning the wisdom of always setting a value for performance toggles. I would think of this more of a hint to unfamiliar users that it is something that exists which they may wish to leverage. Alternatively the library could offer a default set of optimization settings for "above-the-fold" and "below-the-fold" images. However, I feel this obscures knowledge the user should have about how this all works. I think I would keep it basic and fill the gaps with documentation about what setting you probably want for X type of image.

As discussed in #42, gonna close this in favour of documenting in readme, or via a @typedef.

Thanks so much for bringing this up! 🙏