Docs

The reference section. Quickstart got the API running and then got out of your way. This is where you come back when “it worked” stops being enough and you need the exact shape of something — a type, a flag, an error code, the one config option you swore you saw somewhere.

The layers

Three solid nodes you can’t route without, three dashed ones you can delete and RouteGraph won’t notice:

The Scanner walks routes/ once and builds a route table. The RouteGraph class holds it, validated. An Adapter turns that table into something your framework can mount — that’s the whole load-bearing chain. Hot reload, interactive docs, and the typed client are bolted on top, opt-in, and none of them are required to serve a single request.

Progressive adoption

RouteGraph works with zero config: a bare export default handler is a valid route. It gets better as you add more — a config object adds validation, tags add docs grouping, and none of it is required up front. You can adopt one route at a time inside an existing app.