@skmtc/gen-tanstack-query-supabase-zod

Produce Tanstack Query hooks using Supabase's Postgrest-style client as the transport, with Zod validation.

An operation generator. The Supabase-transport variant of gen-tanstack-query-fetch-zod. The entry shape is identical; the variation is in the Projection's toString() (Supabase client calls instead of fetch).

Source

skmtc-generators/gen-tanstack-query-supabase-zod/src/

What it generates

Per operation, hooks that call the Supabase Postgrest client:

export const useGetUsers = () =>
  useQuery({
    queryKey: ['getUsers'],
    queryFn: () => supabase.from('users').select('*').then(({ data }) => userListSchema.parse(data))
  })

Key decisions

Same entry shape as the fetch variant. Same isSupported (GET/DELETE always, POST/PUT/PATCH only with body) and same transform. The only difference is which Projection is invoked — this generator's TanstackQuery produces Supabase calls, the fetch generator's produces fetch(...).
Exports utility helpers (isListResponse, etc.) that other generators import directly. gen-shadcn-select and gen-shadcn-table both import { isListResponse } from '@skmtc/gen-tanstack-query-supabase-zod' to share the list-vs-single response-shape detection logic.
Hardcoded supabase client name. The generator assumes a supabase symbol exists in scope. Customization happens by importing your own client.

What to learn from it

One entry, multiple transports. This generator's existence shows that the entry is transport-agnostic — pick a different client library and you have a new generator with the same shape.
Generator packages as utility libraries. Other generators import from this one (isListResponse). A generator package isn't just an Entry — it can expose reusable helpers other generators consume.

Common customizations when cloned

Swap Supabase for another Postgrest-based client.
Customize the table-name derivation (the stock uses operationId or path; you may want a tag-based mapping).
Add Row-Level-Security parameter passing if your tables expect user IDs in the query.
Change the response-validation step (skip Zod, use a different parser, etc.).