Should non-200 client-side navigations result in a page reload?

If a page errors during SSR…

<script context="module">
  export function preload() {
    this.error(500, 'nope');
  }
</script>

…then the resulting error page is served with the appropriate status code. The same goes for 404s.

But if you navigate client-side from a page that renders ok (/good) to one that doesn’t (/bad), you don’t get an error status code because as far as the browser is concerned you’re not actually navigating.

Remix has an interesting take on this — they actually abort the client-side transition and reload /bad. Is this feature useful? It doesn’t seem particularly useful to me, but they seem quite excited about it so probably know something I don’t.

[Conduitry]

This should possibly be a separate issue, but I do think that there should be a better way to deal with errors when rendering pages (whether on the server or on the client), so you can send them off to some logging service or whatever you want to do. Right now, Sapper is pretty greedy about swallowing errors, and it’s tricky to set something like this up.

A handler like this might also be a good place for someone to implement their own page reload, if that’s something they happened to want.

[benmccann]

Hmm, having the page reload seems like an unexpected behavior to me and it’s probably not what I’d want unless it provides some benefit I’m not thinking of. I’d be curious what the motivation for that feature in Remix is.