Supabase type error when filtering RPC results

[gwax]

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

Supabase supports filtering RPC results via postgrest but the type system shows an error when attempting to do so

Errors show up as Property 'eq' does not exist on type 'PostgrestTransformBuilder<...> but the query still works as expected.

To Reproduce

Minimal reproduction is available in the gwax/rpc-filtering branch here: https://github.com/manapoolinc/supabase-playground/tree/gwax/rpc-filtering

1. Make a table returning rpc: https://github.com/manapoolinc/supabase-playground/blob/gwax/rpc-filtering/supabase/migrations/20250127194033_create_country_fns.sql#L1
2. Query the rpc with a select and a filter: https://github.com/manapoolinc/supabase-playground/blob/gwax/rpc-filtering/src/lib/db/countries.ts#L35
3. See type error in IDE, compiler, linter: https://github.com/manapoolinc/supabase-playground/blob/gwax/rpc-filtering/src/lib/db/countries.ts#L53

Essentially:

const result = await supabase
  .rpc(...)
  .select(...)
  .eq(...); // <-- This causes the error

Expected behavior

No Type Errors in reproduction code

System information

• Version of supabase: 2.6.8
• Version of supabase-js: 2.48.1

[avallete]

Hello there!

We’re working on a fix for this bug and have published a canary release for early testing. If you’re affected, please try it out and let us know if it resolves your issue (or causes any regressions):

# Pin postgres-meta (SETOF introspection)
echo "supabase/postgres-meta:canary-pr-971-40c06b8e011f91c1ae4d2f3d65f2a7c07ad78af8" > supabase/.temp/pgmeta-version

# Install supabase-js canary with updated postgrest-js inference
npm i https://pkg.pr.new/@supabase/supabase-js@749e4d1

# Regenerate types with latest CLI
npx supabase@latest gen types --local --lang=typescript > database.types.ts

Feedback on whether this fixes things (or breaks anything else) would be super valuable!

[gwax]

The canary seems to solve this problem in my minimal test case but I cannot check if it is fully resolved for me until #1364 is resolved. I will be happy to test more later.

[gwax]

This seems to be working for our case but I've updated the reproduction with another, related, error. It's a bit of a stretch, so if you prefer, I'm also happy to consider this resolved and create a new issue.

The issue is if we have a table and a function that returns rows of that table, we can't build a query using a let where the starting point is the same select from the table or the rpc.

[avallete]

This seems to be working for our case but I've updated the reproduction with another, related, error. It's a bit of a stretch, so if you prefer, I'm also happy to consider this resolved and create a new issue.

The issue is if we have a table and a function that returns rows of that table, we can't build a query using a let where the starting point is the same select from the table or the rpc.

Hey!

Thanks a lot for pushing this further and for the detailed reproduction. I think this particular case is a bit out of scope for the fix it comes from re-assigning different query types to the same variable (e.g. a direct select vs. an rpc). At the type level those are treated as distinct, similar to how update and create queries are distinct.

For now, the safest workaround is to avoid reusing the same variable for different kinds of queries.

I’ll keep this issue open until the canary changes are promoted to the stable channel (hopefully soon). Really appreciate you testing this out and sharing feedback it helps a lot in ironing out edge cases.

[gwax]

Thanks for working to get this and the other related issues resolved; they've been keeping us on an annoyingly ancient version of supabase-js and it'll be nice to get back up to date.

I look forward to seeing them released.

[avallete]

This should now be fixed in the latest 2.75.1 version see: https://github.com/orgs/supabase/discussions/39773

Please let me know if you have any more error, and feel free to re-open.