Supabase is no longer supported, maybe

[pilcrowonpaper]

This should've been its own announcement. Really apologize for the sudden announcement. I've decided to remove the Supabase adapter, for now.

The issue is transactions. With the introduction of keys, transactions were required to properly query the database. There's been discussion to add transactions to Supabase and PostgREST (the library behind the Supabase db client) for years, but it's still not supported. It seems Supabase themselves don't intend their library/client to be used in the server, or more accurately, just prioritizing their client side APIs.

That said, I know many people used the adapter, and supporting it isn't a big burden, so I'm open to supporting it again. Just keep in mind that it won't be as reliable as the other adapters.

---

I just want to add that I should've handled this better. Initially I thought it would've been better to just make a decision. I didn't want to publish a package with a hacky implementation, since that goes against what Lucia aims to provide. But I should've just updated the package to 0.6.0, and started a discussion on whether to continue support for Supabase, rather than just making an immediate decision.

Really apologize for breaking the trust between the library author (me) and the users.

[nathanaelphilip]

@pilcrowonpaper supabase has released better SSR support: https://supabase.com/docs/guides/auth/server-side/creating-a-client

[pilcrowonpaper]

No? It's still the same. It works on the server, but latency is much better when using a regular database driver

[Creative-Difficulty]

@pilcrowonpaper pls review @nathanaelphilip 's comment

[Creative-Difficulty]

@pilcrowonpaper cant we just connect to the postgres databse directly like this: https://lucia-auth.com/guidebook/drizzle-orm/#postgres

[Creative-Difficulty]

ok, thanks, that solves the prolem, doesnt it?

[azimari-toure-ikbal]

I have a question with that. I created a project and tried to use lucia with supabase. I'm using drizzle to connect to supabase like shown in the tutorial on lucia but I after everything working fine I get an ERROR from supabase that says CONNECT_TIMEOUT aws-0-eu-central-1.pooler.supabase.com:5432

Is there something i'm missing ?

[Creative-Difficulty]

It appears your URL is wrong

[azimari-toure-ikbal]

The URL should be good I took it directly from my supabase dashboard and I don't have any error regarding wrong connection string.

[natedunn]

Sounds like you have a Drizzle-to-Supabase issue, which doesn't concern Lucia.

[matimusss]

Hi, and before all, I want to thank the developers and community!

I was trying to make some-kind of adapter between postgREST and Lucia, like, instead of connecting to the PG database directly from Lucia, doing it through postgREST API endpoints.

for example:

public async deleteUserSessions(userId: string): Promise<void> { await this.controller.execute( DELETE FROM ${this.escapedSessionTableName} WHERE user_id = $1, [userId] ); }

would be "something like"

- path: /delete_user_sessions
  method: DELETE
  sql: DELETE FROM sessions WHERE user_id = $1

Is that impossible/stupid/nonsensical?

I kinda understood that postgREST was a very good option in terms of scalability, security etc. (bc of heskell?) but I´m don´t have this very clear...

Thanks in advance!!

[osseonews]

postgREST is amazing for this, as you can then just connect to the database at the edge, as all you are doing is writing a fetch request. Highly recommend postgREST. As it forms the foundation of supabase, and supabase supports it (and must), I think postgrest is here to stay, so it's not one of those libs that will just disappear.