Supabase realtime 'postgres changes' fetching number value instead of bigint value

[18vijayb]

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 supabase postgres changes send messages, the bigint id column is being converted to a number

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Set up bigint above max_value for a column value in supabase db
2. Enable anon RLS to access the rows
3. Subscribe to the postgres db channel in javascript according to the tutorial

  supabase
    .channel("schema-db-changes")
    .on(
      "postgres_changes",
      {
        event: "*",
        schema: "public",
      },
      (payload: RealtimePostgresChangesPayload<RealtimePost>) => {
        console.log(payload);
        if (Object.keys(payload.new).length !== 0) {
          console.log(payload.new);
        }
      }
    )
    .subscribe();

Expected behavior

The realtime value for the bigint/int8 column shouldn't be number. I also listened to schema-db-changes in supabase realtime and found the same behavior

Screenshots

System information

• OS: [e.g. macOS, Windows]
• Browser (if applies) [e.g. chrome, safari]
• Version of supabase-js: [e.g. 6.0.2]
• Version of Node.js: [e.g. 10.10.0]

Additional context

Add any other context about the problem here.