Closed chojnicki closed 7 months ago
Please report in the sharp repository
@benmccann but I'm using imagetools, not sharp. So this is correct repository for issue. Especially that author of sharp is saying that this not bug in sharp, but implementation. Even if it is bug in sharp, again, I'm not installing it. It is dependency of this library, so if You think that this version is defective, it should be downgraded here :)
No. That logic doesn't fly with any open source project. Maintainers can't possibly be responsible for bugs in all the libraries that they use. And those libraries also have their own dependencies. Many projects would be responsible for bugs in thousands of libraries at that rate. If you can show we've done something wrong in this project then we can address it. If you're using yarn this may be a duplicate of https://github.com/JonasKruckenberg/imagetools/issues/659. Otherwise there's nothing to suggest there's a bug in this library
I've upgraded Vite 4 to 5 and all plugins, and only imagetools broke.
Of course I'm not going to install sharp manually like advised in console - it's dependency of imagetools so it should work out of the box like before.
I found same issues sharp v0.33, but they are marked as solved because this supposed to be bug with Vercel which was fixed, but Vercel is not used here :P
https://github.com/lovell/sharp/issues/3870 https://github.com/lovell/sharp/issues/3900
What I tried:
It's indeed something with sharp, because when there is 0.33 in lock file it crashesh, but downgrading sharp by downgrading imagetools helps
EDIT: version 6.1.0 also works. In changelog it states that sharp 0.33 was included in 6.2.7 so 6.2.6 should work fine but no, locking it to 6.2.6 still installs latest sharp.