🦋 Changeset detected

Latest commit: 12150e4

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@obennaci still marked as draft, is this ready?

Should be good now 👍

Thanks for opening this, @obennaci!

Looks like I missed the #4341 issue while traveling last week 👀 We're actually still a little too early in the @astrojs/image integration to add more complex transforms to the API right now, unfortunately.

We're working on making Squoosh the default image transformer to add support for web containers and Stackblitz. Sharp will still be an option, but we may paint ourselves into a corner adding support for sharp-specific features early on

I'm going to close this PR for now only because the integration needs a bit more time to bake to make sure the core API surface is the right basis for a 1.0 version of the integration. Hopefully we can pull this back up pretty soon though to revisit how to add more fine-grained transform controls here!

Reopening this PR, we're further down the path towards the Squoosh migration now and I think we should be fine here to add more specific resize options 🥳

@obennaci if you don't mind, I'll get this branch caught up to main and prepped for a final review and merge

PR #4642 came through today and shock loose the sharp vs. Squoosh concerns for me. The APIs are close enough that it won't be a problem to have a few specific checks where the Squoosh loader can just warn that a specific transform option is only supported in sharp

Happy to hear that, can't wait 🥳

On the docs side, it's worth defining the CropFit and CropPosition types, as it currently isn't clear what they represent. You can define them once on the page, and then link to them each time.