Images are broken in the build about overreacted.io HOT 16 CLOSED

7e00945?

from overreacted.io.

I guess we can close this, hasn't happened since. It's still deeply confusing that .cache needs to be cleared before a deploy.

from overreacted.io.

I’ll take a look—thanks for the info!

from overreacted.io.

This was not fixed by #46.

from overreacted.io.

This is really embarrassing. Why does it keep happening?

from overreacted.io.

@gaearon sorry about that! Do you have an example post or posts where this is happening?

Does it only seem to happen on the built site intermittently, or is it something you can reproduce pretty reliably?

from overreacted.io.

It happens on every deploy, in every post with images. (ec340fe is an example)

from overreacted.io.

Seems like bumping deps again (fece90f) may have resolved it. I'll close again for now but if it resurfaces we'll know it's intermittent.

from overreacted.io.

It happened agaaaaain

from overreacted.io.

Clearing node_modules and cache and rebuilding seems to fix it.

from overreacted.io.

So sorry you're seeing this @gaearon

We cache a bunch of stuff in the .cache directory and building (based on your package.json) runs "build": "rm -rf public && gatsby build" which deletes public and not .cache

from overreacted.io.

Sending you a PR in a minute

from overreacted.io.

Right. I thought it's safe to leave the cache but I'll add a thing that clears it.

from overreacted.io.

Perfect

from overreacted.io.

So Netlify's build image at https://github.com/netlify/build-image/blob/65e07189f42d3cc797f1dfe86e197b914a6a5c85/run-build-functions.sh#L41 caches .cache

That's why some builds were failing (mismatch of public and .cache) and some weren't (presumably when you forced a build without cache)

from overreacted.io.

Never mind, that's .cache in the home directory

from overreacted.io.