Exp 09 — nested routes

Three routes under one node.

This heading is rendered by a Layout two levels down from the document. The root Layout wrote the <html> around it; this one wraps every route under /builds, and the component below is whichever one matched.

Layout sees
/builds/nope
Params, from getContext()
{"id":"nope"}

Live specimen — builds/detail.server.tsx

props.params.id
nope
Record
no such build

There is no build under that id, and this page is a 200 anyway. The same lookup at /api/builds/nope answers 404, because a status code is the whole of what an API route says and a Page route has UI to show instead.