gatsby-image generates images for unused components

[vsolanogo]

to improve development start time sometimes i remove all the pages in page folder expect one i will work on, i expect that gatsby image will render images only for those components that it used in that page.js file and its children, but it doesn't, gatsby will render same amount of images, same size of images as it was all pages anyway

Expected result

don't generate images with gatsby image for unused components

Actual result

doesn't matter whether you develop with just single file in page folder (meaninig you deloping only 1 page) or 50 gatsby-image will generate all the images into public folder

[polarathene]

Did you clear out any cache? gatsby clean should work. If you are referring to image graphql queries, I'm not sure how that's handled, but the JS side for gatsby-image components should not be built or included in your bundle. The graphql queries are run at build time triggering the image processing, none of that matters for deployment.

What you want is being tracked here. Unrelated to gatsby-image components.

[vsolanogo]

Did you clear out any cache? gatsby clean should work. If you are referring to image graphql queries, I'm not sure how that's handled, but the JS side for gatsby-image components should not be built or included in your bundle. The graphql queries are run at build time triggering the image processing, none of that matters for deployment.

What you want is being tracked here. Unrelated to gatsby-image components.

of course, i always clear cache

[polarathene]

Clearing the cache will require processing all images again. When developing you can just use gatsby develop and only need to run gatsby clean if something seems broken.

Subscribe to the issue I linked you to, that is what you're wanting for the most part, to avoid unnecessary image processing while developing.

For now you can comment out the graphql queries that you don't want to run, and that will skip them.

[blainekasten]

Closing as duplicate of #24822