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
After updating to version 2.6.0, I encountered an issue when using the getColor method in a Node.js environment. When passing a web image url, the method throws an error: Input file is missing: https://xxxx.xxx/xxx.
Reason
Upon reviewing the source code, I noticed the issue stems from the fact that v2.6.0 now uses sharp for image processing, which does not support directly passing network image URLs. This functionality was available in previous versions, and it became unsupported without a major version update.
Suggestions
I think it would be good to handle network image input internally. This would help maintain backward compatibility. Alternatively, you could mention this change in the release notes. This way, users can understand the cause of the issue. They could then switch to passing a Buffer object or other methods to resolve it.
Anyway, thank you for still maintaining this repository!
The text was updated successfully, but these errors were encountered:
Problem
After updating to version 2.6.0, I encountered an issue when using the
getColor
method in a Node.js environment. When passing a web image url, the method throws an error:Input file is missing: https://xxxx.xxx/xxx
.Reason
Upon reviewing the source code, I noticed the issue stems from the fact that v2.6.0 now uses sharp for image processing, which does not support directly passing network image URLs. This functionality was available in previous versions, and it became unsupported without a major version update.
Suggestions
I think it would be good to handle network image input internally. This would help maintain backward compatibility. Alternatively, you could mention this change in the release notes. This way, users can understand the cause of the issue. They could then switch to passing a Buffer object or other methods to resolve it.
Anyway, thank you for still maintaining this repository!
The text was updated successfully, but these errors were encountered: