fix: revert sharp to 0.32.6 for Vercel templates #14153
Open
+1
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rgbjoy
changed the title
rgbjoy
changed the title
rgbjoy
changed the title
rgbjoy
changed the title
rgbjoy
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Discussed here:
vercel/next.js#83230
a simple create-next-app with sharp being used in simple example: https://github.com/rgbjoy/vercel-nextjs-turbopack-sharp
Deployed: https://vercel-nextjs-turbopack-sharp.vercel.app/
Building this locally and on a vercel deployment is fine. VIsiting one of the sharp examples shows the 500 error: https://vercel-nextjs-turbopack-sharp.vercel.app/api/thumbnail?w=240&format=webp
Discord community help post: https://discord.com/channels/967097582721572934/1425735616913477683
Downgrading sharp from 0.34.4 to 0.32.6 resolves Vercel deployment issues caused by incompatible native binaries in newer sharp releases. Version 0.32.6 includes prebuilt binaries that match Vercel’s current Node runtime, making it the stable choice until Vercel updates its build image.