GraphQL Query Error caused by coverImage about gridsome-starter-blog

[seanogdev]

Is there a workaround for this, @hjvedvik?

[hjvedvik]

I see. Gridsome creates the GraphQL schema based on fields it finds at startup, so that's probably why the coverImage isn't an image field sometimes. We are working on a solution to make Gridsome remember the schema instead of just looking up fields on nodes every time you start the development server, but it's not ready yet :)

[lauragift21]

No I haven't yet. I'm hoping the fix get merged in soon enough.

[Xstoudi]

Is there an update about this issue ? How can I re-generate the GraphQL schem ?

[eleijonmarck]

@Xstoudi @miralize Have you tried?

rm -rf node_modules
rm -rf .cache

[hjvedvik]

Does this happen while the development server is running or when you start up again after deleting a post?

[lauragift21]

It happens when I delete the post and start up the server again.

[lauragift21]

Alright, that makes sense. Looking forward to that fix.

[SamUndefined]

@lauragift21 Have you by chance found a decent workaround in the meantime?

Locally, I've been deleting those arguments, starting the server, and then re-adding them after reboot. On (Netlify) deploy, I just run re-run the build until it works 😬

[kendallroth]

I've had this happen whenever I change the image path in frontmatter as follows:

# Builds and displays
cover_image: /images/test.jpg

# Builds but does not display image (doesn't exist?)
cover_image: ./images/test.jpg

# Doesn't build and displays this error (path saved by Netlify CMS)
cover_image: images/test.jpg

[dizid]

Here is a plugin that might fix this error

[RehanSaeed]

I'm getting this error on GitHub actions when doing a build, not develop. Is there any workaround?

[RehanSaeed]

Did you find a resolution? I raised gridsome/gridsome#1031.