Hi folks - Y’all are working together, right @TravisBallardand @skogsmaskin?
Anyway, sorry Travis, I do see a package.json there and I do see it being used in builds on the site such as https://app.netlify.com/sites/andrews-powdercoating/deploys/5d4f7847132462d7b74f61a0 - not sure what I was looking at before, perhaps a wrong deploy in another site!
@skogsmaskin that’s pretty expected behavior - not that the cache wouldn’t work, but that any use of a build hook would use a cache, since the only way to clear the cache is via our UI and thus you clear it there and then that build finishes and we save the cache and it is there for your hook-triggered build (unless you can get that hook triggered build to start before the other one finishes maybe?)
Anyhow it is not particularly surprising that lerna & monorepo projects with package.json’s in other directories aren’t building right since our support for them is pretty much nonexistent: https://github.com/netlify/build-image/issues/196 , but we are working on the next iteration of our build network which will handle them better.
For today, I think clearing the cache manually is going to be your best path for deploying such a site here, but you may be able to figure out some better workaround by using our build image locally to try different settings for the
base directory and tweaking package.json layout: https://github.com/netlify/build-image#running-locally .
You’ll probably be most interested in tracking that issue in the build-image repo so you can try the new system once it is available (it’s getting close to testable now :))