Types and tooling

What exists

Everything on questpie/services is also on the bare questpie entry.

Inferring a route's types

On a JSON route the helpers read the definition's schema members, not the handler. That matters. Codegen erases handler bodies, and these types still resolve afterwards.

import type {
	InferRouteInput,
	InferRouteOutput,
	InferRouteParams,
} from "questpie/types";

import type createBooking from "@/questpie/server/routes/create-booking.post";

type Input = InferRouteInput<typeof createBooking>;
type Output = InferRouteOutput<typeof createBooking>;
type Params = InferRouteParams<typeof createBooking>;

InferRouteOutput falls back to unknown when it can recover nothing, never to any. So you have to narrow it, instead of quietly getting it wrong.

Params from the file name

RouteParamsFromKey derives params from a route key, brackets and method suffix included. Codegen uses it so client.routes.* types a [id] route correctly, without your handler having declared anything.

type P = RouteParamsFromKey<"users/[id]/posts:GET">; // { id: string }
type Q = RouteParamsFromKey<"auth/[...path]:POST">; // { path: string }

This types the generated surface, not your handler body. Inside the route file you still declare .params<{ id: string }>().

Running a route without HTTP

executeJsonRoute and executeRawRoute run the same pipeline the HTTP handler runs: parse, access check, handler inside the context scope, output check. Use them in a test, a script, or one route calling another.

import { executeJsonRoute } from "questpie/services";

import subscribe from "@/questpie/server/routes/subscribe.post";

const result = await executeJsonRoute(app, subscribe, {
	email: "ada@example.com",
});
// result: { id: string; status: "subscribed" }

Arguments 4 and up are optional. Pass no context and the call runs with accessMode: "system", which is the right default for a script. Pass one from a real request and the route sees that caller's session.

Listing every route

introspectRoutes(source) flattens the routes tree into an array sorted by key. @questpie/mcp reads it to build its tool list. It takes the app, a { routes } object, or the bare tree.

import { introspectRoutes } from "questpie/introspection";

const routes = introspectRoutes(app);

methods is always an array, even for the single-method route that one file produces.

Related

• Client SDK, where these same types land for the caller.
• Codegen, what erases the handler and why the helpers are built to survive it.