Output 404 in dynamic segment route page

[nsams]

When the slug of a segment route page isn't found I want to render a not-found page.

I can easily render some not-found content, but how do I get a 404 http response code?`

[dai-shi]

Right now, we don't provide an explicit way because react components can't always send 404 response.

I'm not sure what will be best practice, but one of ideas will be:

• Throw an error in a server component
• Catch it in an error boundary (in a client component)

Even though we could respond with 404 for SSR, RSC with 404 might not be handled well.

Any thoughts? @tylersayshi @rmarscher @pmelab

[dai-shi]

I'm pretty sure they throw special error types inside their notFound and redirect functions that their server and client-side routers know how to handle.

Alright, so it's not the exceptional error that I meant, but it's a special error to handle it properly.
That's quite a bit of work. I wonder in which layer I'd implement it in Waku. Let me think about it.

[dai-shi]

#1247 is the minimal api for this.
For the router api, we need to make sure to use our custom error boundary. So, #1131 was a bad move.

[rmarscher]

Maybe it could be possible for our custom error boundary to handle these special errors and let the rest pass through -- or let the dev pass in a function or component to handle the other types of errors if they want. My issue in #1131 was that the error boundary wasn't doing enough and wouldn't let me customize the fallback output.

[dai-shi]

let the rest pass through

That would be great. Does rethrowing the error in the first error boundary work?

[dai-shi]

#1261

Hope someone can try the experimental capability.