"gatsby-plugin-extract-image-colors" threw an error while running the onCreateNode lifecycle

[gfrcsd]

Hey,

Facing this issue while using gatsby-plugin-extract-image-colors and had no luck troubleshooting it. My implementation seems correct too as it runs fine on development server locally (despite the error showing) but fails to build.

I have already tried to add node-vibrant@3.2.0-alpha and reinstalled all dependencies

Any help would be greatly appreciated

Error Message

ERROR #11321  PLUGIN

 "gatsby-plugin-extract-image-colors" threw an error while running the onCreateNode lifecycle:

Cannot read property 'Vibrant' of undefined

  38 |       yield Vibrant.from(node.absolutePath).getPalette((err, palette) => {
  39 |         const colors = {
> 40 |           vibrant: getHex(palette.Vibrant._rgb),
     |                                   ^
  41 |           darkVibrant: getHex(palette.DarkVibrant._rgb),
  42 |           lightVibrant: getHex(palette.LightVibrant._rgb),
  43 |           muted: getHex(palette.Muted._rgb),

Relevant GraphQL

frontmatter {
  image {
    colors {
      ...GatsbyImageColors
    }
    childImageSharp {
      fluid(maxHeight: 450) {
        ...GatsbyImageSharpFluid_tracedSVG
      }
    }
  }
}

[robations]

I have the same here. It seems to skip past these errors with the dev server, but breaks production builds.

I'd guess we just need to check if the err parameter is set and then either set colors to be an empty object (or perhaps null?).

I can send a PR if @mittnavnermike is open to this.

[robations]

NB As well as checking err, it's also necessary to check that the palette properties are not null.

I'm not sure if Mike is still alive so I've forked this as a local plugin and effectively applied optional chaining and adjusted function getHex() to avoid build errors. This means that some colors may be returned as null, but, in any case, this is the default for graphQL.

[mittnavnermike]

Hey guys! PR's are very welcome! I'm not using gatsby anymore so I personally won't be maintaining these packages.

[robations]

@mittnavnermike Glad you're still with us. I'll likely be too busy this week, but if I manage to circle around I'll submit a PR with my local changes. I'm hoping Gatsby becomes more sane, a bit of a mixed bag of good and bad at the moment.

[el-j]

is this still open? i just have this error when the image is missing. so it seems ok to fail.

[robations]

IIRC I inlined the plugin into my project with a few tweaks (under time pressure). I could dig this out if it would be useful.

I'm usually on board with "fail fast", but in my case, I had lots of errors with images that had moved or with wrong links in the content, so it was going to be frustrating to spend ages fixing hundreds of random content issues when I was supposed to be building a site. Content issues could be fixed later, hopefully by someone else...