Hi, @donovan, the Netlify CLI tool doesn’t use a local cache. If something is being cached, it is being cached by your local build tools and not the CLI tool.
I could be misunderstanding what you are trying to do. If so, more details about your workflow might help us to better answer this question.
So the ElasticLunr plugin for Gatsby rebuilds its index with each gatsby build.
But if I run netlify build, it doesn’t rebuild the index (even though it’s basically still running gatsby build).
In order to get it to rebuild the Elastic search index, I have to first run gatsby build on its own, and then run netlify build && netlify deploy.
It’s weird I know. I’m not sure why this is happening. I assumed it was something to do with Netlify incremental builds and Gatsby basically skipping the Elastic search index because it’s cached.