Removing gatsby clean from gatsby build process

[LarsBehrenberg]

Feature request

I am currently running a Gatsby w/ NetlifyCMS site and have been looking for a workaround so I don't have to run gatsby clean every time after changes have been made in the CMS => meaning removing the gatsby clean from the build command.

What is the expected behavior?
Running gatsby from cache, keeping already formatted images and only rebuild pages where changes have been made.

What is motivation or use case for adding/changing the behavior?
Due to the large number of images on my site, having to rebuild every time from scratch takes a lot longer than it should.

How should this be implemented in your opinion?
The problem seems to be that images cannot be found after changes have been made to the md file resulting in "Cannot read property 'childImageSharp' of null". So far only removing the cache and public folder seems to resolve the issue, but this comes with long building times.

Are you willing to work on this yourself?
yes

[ZoltanVeres]

The only viable option i see is do what Jason wrote in this article about enabling Gatsby incremental build. Please post back to us if you happen to go down this path

[kenfehling]

I was having a similar issue, seemingly identical to this error. I updated gatsby-remark-relative-images to version 2.0.2 and that fixed it for me. Pull Request 621 is already open for bumping that dependency.