Generating typed TypeScript and Python code from Supabase SQL queries

A lot of Supabase work is plain SQL against Postgres. If you write those queries and then hand-type the results (or lean on generated client types that miss join nullability), this might help. I maintain scythe, which reads your .sql files and generates typed client code at build time. It infers nullability from the query, which the schema-level type generation usually misses:

-- @name GetUserOrders
SELECT u.id, u.name, o.total, o.notes
FROM users u
LEFT JOIN orders o ON u.id = o.user_id
WHERE u.status = $1;

// generated TypeScript
interface GetUserOrdersRow {
    id: number;
    name: string;
    total: string | null;
    notes: string | null;
}

total and notes are nullable because the LEFT JOIN can produce NULLs, even though the columns are NOT NULL in the table. It generates both TypeScript and Python, so a Supabase backend and a data script can share the same query definitions.

This is complementary to Supabase's own type generation, not a replacement for the client. Interested whether people here hit the join-nullability gap in practice.