GatsbyJS and the Sharp plugin

• Link to my GatsbyJS and the Sharp plugin podcast on anchorfm

Yesterday I updated my GatsbyJS site to 2.18.16 and Node.js to 12.14.0, but I had to remove the gatsby-plugin-manifest and the gatsby-plugin-offline due to deduping of the sharp plugin dependency.

This morning I did some further research on sharp andgatsby. I found the following section in the GatsbyJS docs:

• gatsby-plugin-sharp

Here, I learned (and possibly it was a re-learn that I forgot) that when plugins that depend on the sharp plugin have been updated, all the other plugins that depend on sharp have to be updated as well:

you’ll need to update all Gatsby plugins in the current project that depend on the sharp package. Here’s a list of official plugins that you might need to update in case your projects uses them:

- gatsby-plugin-sharp
- gatsby-plugin-manifest
- gatsby-remark-images-contentful
- gatsby-source-contentful
- gatsby-transformer-sharp
- gatsby-transformer-sqip

It turns out that I had to update gatsby-plugin-sharp and gatsby-transformer-sharp since I had updated gatsby-plugin-manifest! That’s why deduping was occurring. Not all plugins that depended on sharp in my GatsbyJS repo had been updated.

I updated the two sharp dependent plugins and ran

npx gatsby build

My build was successful locally. There was no deduping of sharp.

Then I deployed the changes to Netlify. My deploy to remote was successful.

I will be embedding this episode of Plugging in The Holes along with a transcript in the form of a post on interglobalmedianetwork.com for your hearing and reading pleasure. I will be including the related resource links mentioned in the podcast of course. Always do. Bye for now!

• GatsbyJS 2.18.16
• When the Homebrew command brew update fails
• gatsby-plugin-sharp
• interglobalmedianetwork.com repo