Supabase

[ghost]

SUPABASE

👉AUTH AND RPC

Hello everyone,

I wanted to propose an idea for integrating Supabase authentication into Vike, structured in two parts:

1. API routes with Hono — for handling user authentication, like fetching the current user and signing out.

2. Sign-in using Telefunc (RPC) — to allow secure and flexible client-server communication.

I’ve already started an implementation that works, but given Supabase’s growing user base — especially with the recent introduction of Cursor ecosystem— it would be great to establish a clean, secure, and maintainable integration.

Standardizing best practices for Supabase authentication in Vike would not only simplify onboarding but also help ensure consistent security patterns across projects.

🙂
Would love to hear your thoughts!

Homepage

https://supabase.com/docs/guides/auth/server-side/creating-a-client?queryGroups=framework&framework=hono&queryGroups=package-manager&package-manager=pnpm&queryGroups=environment&environment=server-client

[ghost]

Hello everyone,

I wanted to propose an idea for integrating Supabase authentication into Vike, structured in two parts:

1. API routes with Hono — for handling user authentication, like fetching the current user and signing out.

2. Sign-in using Telefunc (RPC) — to allow secure and flexible client-server communication.

I’ve already started an implementation that works, but given Supabase’s growing user base — especially with the recent introduction of Supabase Cursor — it would be great to establish a clean, secure, and maintainable integration.

Standardizing best practices for Supabase authentication in Vike would not only simplify onboarding but also help ensure consistent security patterns across projects.

Would love to hear your thoughts!

[magne4000]

Hello @br0wsa, thank you for wanting to help improve Bati!

1. API routes with Hono — for handling user authentication, like fetching the current user and signing out.

We'll have a portable (as in not tied to a specific server) way to handle things like API routes when vike-server 1.0 releases. No ETA yet, but I'm actively working on this subject.
You can take a look at the telefunc middleware to see what it will look like.

2. Sign-in using Telefunc (RPC) — to allow secure and flexible client-server communication.

The objective with Bati is to give users a choice, so usually we try our best to not force a specific library onto the users. That would mean in that case that we also need to support tRPC and ts-rest.

Standardizing best practices for Supabase authentication in Vike would not only simplify onboarding but also help ensure consistent security patterns across projects.

Seems like a reasonable expectation.
As the amount of integrations in Bati is growing, I'll need to rely on the community to maintain some of them.
So I have 2 questions for you.
Do you want to implement this integration?
If yes, would you be willing to be considered as the official maintainer? Your responsibilities would be to ensure that potential bugs related to Supabase are fixed, and also update the codebase in case of Supabase package update breaking things.

[ghost]

Yes, yes.

Hello @magne4000,

Thank you for your message and for the opportunity to help improve Bati! I am interested in the integration, but I want to mention that Vike is new to me. Currently, I am encountering a bug that is preventing me from adding the user to the context. I hope to resolve this issue and contribute to the integration effectively.

Actually I can't pass the user context coded with hono to the Vike handler. the rest will be done with telefunc.

Thanks again for your trust!

Best regards,

[ghost]

Help: Integrating Supabase Auth with Vike (via Bati + Hono + Universal Middleware)

Hi everyone,

I'm currently building an app using Bati which scaffolds Vike-based projects. The generated setup includes @universal-middleware/core for SSR middleware handling.

I've noticed this in the boilerplate code:

`// TODO: stop using universal-middleware and directly integrate server middlewares instead and/or use vike-server https://vike.dev/server. // (Bati generates boilerplates that use universal-middleware https://github.com/magne4000/universal-middleware to make Bati's internal logic easier. This is temporary and will be removed soon.)

I want to integrate Supabase authentication using @supabase/ssr. I'm currently doing this through a custom Hono middleware that injects supabase and user into the universal context using return { ...context, user, supabase }.

Questions

1. Are there any major changes coming in Vike 1 that would affect this kind of integration?

2. Should I continue with this setup or wait for official vike-server support and migrate away from universal-middleware when it's stable?

3. Is there any plan to support Supabase officially in Vike or in the Vike ecosystem?

Thanks in advance for your insights and suggestions!

[magne4000]

Are there any major changes coming in Vike 1 that would affect this kind of integration?

You will be fine. Either Hono middlewares or Universal ones will still be usable in the future.

Should I continue with this setup or wait for official vike-server support and migrate away from universal-middleware when it's stable?

Do not worry, going to and from vike-server should be done in a couple of minutes.

Is there any plan to support Supabase officially in Vike or in the Vike ecosystem?

I really like Supabase stack, so I would like to have some kind of top tier support for it, but I really do not have the bandwidth to do this on my own. For this kind of integrations, we must rely on contributors like you for now.

[magne4000]

feat: Add Vike + Hono + Supabase SSR example with middleware and client