fix(deps): Update Sharp optionalDep version

[Princesseuh]

Changes

I'm not too sure, but I think this is the cause of all the recents Sharp-related issues like #9345

Since Sharp changed its installation method in its latest version, mixing versions can get weird and certain package managers seems to have issues handling it. I've never been able to reproduce any issues, so I can't really tell what the problem is, nonetheless I believe this should fix it!

Testing

Can't really test if it fixes the issue or not, but it should still work.

Docs

N/A

[changeset-bot]

🦋 Changeset detected

Latest commit: d0f9198

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

[jlarmstrongiv]

@Princesseuh unfortunately, the latest version of sharp still breaks when bundling deployments, see vercel/ncc#1153

Would you allow the installation of an older version of sharp (specifically, at least 0.32.6) for the time being?

[Princesseuh]

@Princesseuh unfortunately, the latest version of sharp still breaks when bundling deployments, see vercel/ncc#1153

Would you allow the installation of an older version of sharp (specifically, at least 0.32.6) for the time being?

It's an optionalDep, so you should be able to install whatever version of Sharp you prefer, I think!

[jlarmstrongiv]

It seems sharp@0.33.1 is still being installed for me, but I have a different workaround to force 0.32.6 for the time being