Chris Gwilliams

@aantn glad this solves your problem! For the docs, how would you like to see them improved: - clarification on identities table? - clearer information about the client_metadata vs app_metadata?...

Thanks for reporting, please make sure you contact the Logflare support email as well! This is happening when viewing logs in the dashboard or when viewing them through logflare?

@vulrun Was this resolved via Support ticket or is this still occurring?

@vulrun can you provide the Ticket Number that you opened so I can check the progress? 🙏

Thanks for reporting! As this is erroring on `node-fetch`, please open the issue there. Also, the version of Supabase JS is at 2.39.6 so it is worth updating it.

It is occurring there, yes, although it is occurring there due to how Shoelace is loading it (or Webpack) `node-fetch` is a package that runs within node runtimes so it...

``` Frontend Supabase class SupabaseClientComponent extends HTMLElement { constructor() { super(); this.supabaseUrl = ''; this.supabaseKey = ''; this.supabase = null; } connectedCallback() { this.initializeSupabase(); } initializeSupabase() { this.supabase = supabase.createClient(this.supabaseUrl,...

Apologies, that is not the point I was trying to make. The point (if any) was to show that this is not a Supabase issue; it is a bundler/webpack/ESM issue...

Hi @buildWithSoul yes please, feel free to open a PR! Thanks for reporting

Thanks! No need to assign, you can just open a PR and mention this issue :)