"Loading the component for ${page.path} failed" after new build deployed

I’ve noticed the following scenario can happen:

1. Build & deploy gatsby site to S3 via sync (missing files get deleted from bucket)
2. Load site in browser
3. Edit some /page/name.js
4. Repeat step (1)
5. With same browser session from (2), navigating to the edited page via a link can fail, with the error in the console: Loading the component for /page-3/ failed from loader.js

Intuitively, I understand why this is happening - the new build has changed the resource for the edited page so the previous one is removed from the server upon sync.

Is it be possible for the loader to handle this scenario? Possibly by attempting a regular ol’ http request of the path, causing the app to reload and refresh the pre-cached references?

[KyleAMathews]

Sweet!

I just meant that within loader track failures. If some downloads are succeeding while some are not, this means the user is definitely online just that they’re fetching older versions of the site some which no longer exist so you should refresh.

[Chuloo]

There hasn’t been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues as many of them have already been resolved with the latest updates or explained in a previous issue.

Feel free to open a new one if you still experience this problem or a similar one! 👍