By default, Node `SupabaseClient` leaks itself due to `SupabaseAuthClient` `setInterval` about supabase-js HOT 4 OPEN

Yep, setting autoRefreshToken to false works for us. My only complaint is that the default failed silently in a nasty way and there wasn't really any documentation calling out what I needed to do in a server context for it to be OK, so it seems like there could be room for improvement. For example, the code could interpret the default autoRefreshToken: undefined like true in a browser and false on Node, although maybe that would trick other people, who might use a single-long-lived client whose access token expires after a while.

from supabase-js.

I'm guessing you're not using an auth helper package to create the client.

If using the native createClient function, you'll want to set these auth options for that server client.

autoRefreshToken: false,
detectSessionInUrl: false,
persistSession: false

This is assuming that you're not keeping track of a user session with this client.

from supabase-js.

Yeah I think there used to be a small blurb about this in the docs, but I can't find it now.

They could set it up to be automagic based on a browser context - this is what auth helpers/ssr does - but that would be a breaking change for the native client function.

from supabase-js.

@mqp these are good points - perhaps we could use something like FinalizationRegistry to register a cleanup method when the class is instantiated on the server-side.

although it seems like they have a huge warning too :/ (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/FinalizationRegistry#avoid_where_possible)

from supabase-js.