You might want to have a look at Remix [0]. I haven't used it extensively myself, but it does claim to handle errors well.

> Route Error Boundaries keep the happy path happy. Each route module can export an error boundary next to the default route component.

> If an error is thrown, client or server side, users see the boundary instead of the default component. Routes w/o trouble render normally, so users have more options than slamming refresh. If a route has no boundary, errors bubble up. Just put one at the top and chill out about errors in code review, yeah?

[0] https://remix.run