Description
Possible bug
Is this a possible bug in a feature of sharp, unrelated to installation?
- Running
npm install sharp
completes without error. - Running
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?
- I am using the latest version of
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
?
System:
OS: macOS 15.1
CPU: (11) arm64 Apple M3 Pro
Memory: 216.06 MB / 36.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 22.11.0 - /usr/local/bin/node
pnpm: 9.10.0 - /usr/local/bin/pnpm
bun: 1.1.12 - /opt/homebrew/bin/bun
npmPackages:
sharp: ^0.33.5 => 0.33.5
Does this problem relate to file caching?
The default behaviour of libvips is to cache input files, which can lead to EBUSY
or EPERM
errors on Windows.
Use sharp.cache(false)
to switch this feature off.
- Adding
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?
Download this png
curl -JO https://images.bookroo.com/site/landing/homepage/book-collection.png
Then run the following code:
const sharp = require('sharp');
const fs = require('fs');
async function main() {
const buffer = fs.readFileSync('./book-collection.png');
const start = performance.now();
const optimizedBuffer = await sharp(buffer).resize(1850).avif({ quality: 55 }).toBuffer();
console.log(performance.now() - start);
return optimizedBuffer
}
main().catch(console.error);
What is the expected behaviour?
Should take about 800ms but it actually takes 2700ms.
You can see the difference if you change .resize(1850)
to .resize(1849)
.