-
Notifications
You must be signed in to change notification settings - Fork 10.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
Improve sharp upgrade experience when libvips is upgraded #16985
Comments
If working with
And
doesn't prevent yarn to install sharp
creates divergences in the different packages of the workspace
So I also downgrade
delete which gives me
and then,
And now I don't know what else can I try |
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here. Thanks for being a part of the Gatsby community! 💪💜 |
Hey again! It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it. Thanks again for being part of the Gatsby community! 💪💜 |
Currently upgrading
gatsby-plugin-sharp
(or rather its dependencysharp
) when there is a version change to the underlying libvips dependency is a little problematic because it fails with #16957 unless annpm rebuild
is run.@lovell had some lovely recommendations in lovell/sharp#1680 (comment) on how to tackle this.
We have to some extent in https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-plugin-sharp/src/safe-sharp.js but it appears that we'll have to handle this corner case as well
CC @pieh
The text was updated successfully, but these errors were encountered: