Load failed on data loaders for routes results in landing in the Error boundary --- is there a better way to catch and retry these?

[allenjiang17]

Hi,

Network connection issues or other fetch issues with fetching to a route's data loader will automatically escalate up to the error boundary. I'd like to be able to handle some of these, because if some of these fetch errors are just a network connection problem, then ideally I'd like to have some kind of retry mechanism before showing the user the error boundary page.

This is kind of related to this previously closed issue, but for the more general case of fetch calls to any route's data loader, instead of loading from useFetcher.

One idea would be to monkey patch the client-side fetch API with retries and let Remix use that fetch API to make all loader/action requests, but I'm hoping for something more graceful than that...

[NinjaLukeI]

I agree, I definitely have come across this issue and need a fix for this as well or some sort of workaround