fix: default Database generic to any, matching createClient()

[mandarini]

Defaults the Database generic to any instead of unknown across every client-creating function (withSupabase, withSupabaseClient, withSupabaseAdminClient, createSupabaseContext, createContextClient, createAdminClient, and both the Hono and Elysia adapters), plus SupabaseContext itself. Previously an unannotated write failed type-checking, for example ctx.supabase.from('t').insert({...}) resolved to not assignable to parameter of type 'never', forcing every untyped consumer into a withSupabase<any>(...) workaround just to compile.

This matches createClient() in @supabase/supabase-js, which has always defaulted its own Database generic to any. Nobody loses type safety who wants it: pass generated database types the same way as before, withSupabase<Database>(...), and every table and RPC call stays fully typed. Only the unannotated path changes, from a compile error to a permissive default.

The any default is centralized in one named alias, UntypedDatabase, in types.ts, rather than repeated as a bare any at each call site. Docs (typescript-generics.md, api-reference.md, adapters/nestjs.md) are updated to match.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@supabase/server@156

commit: 8f19dfa