Correct types are not returned for custom schemas

[Cayllen]

Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

When setting the custom schema on supabase client initialization, all subsequent calls had previously the right types. Now with some last update of the supabase (schema generation I think), this does not work anymore and I would need to additionally set the relevant schema on every call.

Expected behavior

Only setting the custom schema once at the initialization of the client

Screenshots

Here the return type is any

If I additionally set the custom schema on the prompt, it works

System information

• Version of supabase-js: "2.52.1",
• Version of Node.js: 22.16.0

[krishvsoni]

@Cayllen Is anyone working on this issue ?

[Hallidayo]

Hi, I've moved this issue over from the supabase repo.