Analyzer::Javascript::Hono

<receiver>.on('GET', '/path', …) (method in group 2) or .on(['GET', 'POST'], '/path', …) (group 3); the path is group 4. Any receiver (books, api, …) with a / or * path — an event name is neither — except the usual event-emitter names, whose .on('get', '/room/1', cb) has the same shape.

@hono/zod-openapi: createRoute({ method, path, request }) declares a route (served once handed to app.openapi(...)), and app.doc(path) serves the generated spec. Routes are reported where they are declared, under that file's mount prefixes. ponytail: a createRoute in a *.routes.ts takes that file's prefixes, not those of the router that registers it; follow .openapi( imports if those prefixes turn out to differ in practice. db.doc('users/1') (Firestore and friends) is the same call shape on a different receiver. Only an app built with new OpenAPIHono / new Hono.

Compiled once — an interpolated regex literal would otherwise be rebuilt (full PCRE2 compile) for every method on every line.

Instance-side view of the same declaration. The per-file rescues live on this base class, which has no way to name the analyzer that is running inside them, so a skipped file could not be attributed to a tech. Deriving it from analyzer_for keeps the name written exactly once.