-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[email protected] fails to compile with NextJS 15 (works with [email protected]) #4361
Comments
There's a lot going on here. Please can you simplify/reduce the steps required to reproduce this, perhaps as a standalone repo, and without a dependency on third party services. |
Astro, same thing locally on Ubuntu. |
Same here, but only in production. Related: |
Please can someone produce a complete, minimal, standalone repo that allows someone else to reproduce. |
After upgrading to 0.34.1 build fails with this error in WP Engine: I can build locally without any issues on my Windows machine. To make it work in WP Engine, I downgraded sharp to 0.33.5 version. |
Clear, simple steps for someone else to reproduce is the only thing that's going to help here.
If you see the mention of |
Some global OS package is missing in Ubuntu 24.04 desktop, in the next few days I will see which one exactly. It works in more complete Linux images. |
Vercel fixed it.: vercel/next.js#77839 |
I'm using |
@JonBernardHealia As creator of this issue, were you able to make any progress with this? |
Possible bug
Is this a possible bug in a feature of sharp, unrelated to installation?
npm install sharp
completes without error.node -e "require('sharp')"
completes without error.If you cannot confirm both of these, please open an installation issue instead.
Are you using the latest version of sharp?
sharp
as reported bynpm view sharp dist-tags.latest
.If you cannot confirm this, please upgrade to the latest version and try again before opening an issue.
If you are using another package which depends on a version of
sharp
that is not the latest, please open an issue against that package instead.What is the output of running
npx envinfo --binaries --system --npmPackages=sharp --npmGlobalPackages=sharp
?Does this problem relate to file caching?
The default behaviour of libvips is to cache input files, which can lead to
EBUSY
orEPERM
errors on Windows.Use
sharp.cache(false)
to switch this feature off.sharp.cache(false)
does not fix this problem.Does this problem relate to images appearing to have been rotated by 90 degrees?
Images that contain EXIF Orientation metadata are not auto-oriented. By default, EXIF metadata is removed.
To auto-orient pixel values use the parameter-less
rotate()
operation.To retain EXIF Orientation use
keepExif()
.Using
rotate()
orkeepExif()
does not fix this problem.What are the steps to reproduce?
What is the expected behaviour?
Docker build logs
Partial Dockerfile
The text was updated successfully, but these errors were encountered: