You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using .trim().toFile() it will return a metadata object, which includes the trimOffsetLeft and trimOffsetTop properties.
When we instead save to buffer with .trim().toBuffer() no such properties will become available on the response object.
While I am not sure what is happening in the background, I believe that the offset data is available before saving the image (as this data is used in the operation itself) so it should also be available on the final returned object.
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 by npm view sharp dist-tags.latest.
The text was updated successfully, but these errors were encountered:
Possible bug
When using
.trim().toFile()
it will return a metadata object, which includes thetrimOffsetLeft
andtrimOffsetTop
properties.When we instead save to buffer with
.trim().toBuffer()
no such properties will become available on the response object.While I am not sure what is happening in the background, I believe that the offset data is available before saving the image (as this data is used in the operation itself) so it should also be available on the final returned object.
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
.The text was updated successfully, but these errors were encountered: