Closed RamyaChinnadurai closed 1 month ago
Same issue here
TypeError: ue.PostgrestClient is not a constructor at new j (SupabaseClient.ts:106:17) at Oe (index.ts:42:10) at main.js:5:18
I also ran into this today when deploying a new edge function. The deploy was successful, but calling the EF always results in an error code 546 and the message:
event loop error: TypeError: ue.PostgrestClient is not a constructor
at new j (https://esm.sh/v135/@supabase/supabase-js@2.43.3/deno/supabase-js.mjs:12:5741)
at Oe (https://esm.sh/v135/@supabase/supabase-js@2.43.3/deno/supabase-js.mjs:12:9156)
Same issue here. I solved by downgrading to the previous version.
Started receiving this error today as well:
ue.PostgrestClient is not a constructor
Was importing as:
import { createClient } from 'https://esm.sh/@supabase/supabase-js';
Now working by rolling back to:
import { createClient } from 'https://esm.sh/@supabase/supabase-js@2.43.2';
similar error, I had the following:
import { PostgrestError } from '@supabase/supabase-js'
was working fine, didn't make any changes, now I get:
Type error: Could not find a declaration file for module '@supabase/supabase-js'.
Hi all, I had the same issue, I just used a diff version in my import statement and it worked out. in my case it was
import { createClient } from 'https://esm.sh/@supabase/supabase-js@2.43.1'
did not change anything else
Starting this morning, I began encountering the error
PostgresClient is not a constructor
despite not making any changes to my code.I'm currently using
@supabase/supabase-js: 2.12.0
.I suspected that the issue might be related to a recent update in one of the dependencies. Turns out
supabase/postgres-js
updated in the last 24 hoursAs a temporary workaround, I have forced the use of a previous version of the dependency by adding the following to my package.json:
Looking for a permanent solution for this case