feat: Supabase Auth Example #1830
Conversation
V1 of the utilities, leaning SolidStart as I go Register middleware Actions, Pages, Components WIP - Struggling with Sessions Start over Still in the untested stage finishing up the initial code Delete old version Testing Improving styles, accepting broken navigation Pulling out signOut and getUser Trying things with navigatiotn
|
✅ Deploy Preview for solid-start-landing-page ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
Hello. First of all, sorry it took us so long to look at this. Part of this is the issue is that we've been looking at how to better server the community with our templates and ongoing repo work. Because of that we have decided to move templates to [solidjs/templates](https://github.com/solidjs/templates). You're much welcome to recreate this template there, and read more on the new architecture in the discussion #1984 You're feedback is definitely much appreciated. 💙 |
2 participants
PR Checklist
Please check if your PR fulfills the following requirements:
What is the current behavior?
There is no complete example for how to use Supabase in SolidStart.
What is the new behavior?
Create a "complete" example of Supabase Auth with the following features
Other information
This is actually my first non-trivial work with SolidStart, so I'm sure there are some non-idiomatic things I can improve.
One of the biggest problems I encountered was the inability to create an isomorphic Supabase client. I had a lot of unpredictable behavior until I strictly separated the server and client code. I blame this one line in the docs:
Since I use Vinxi functions when instantiating a Server Supabase client, the normal isomorphic pattern of
isServer ? doServerThing() : doClientThing()didn't work. Maybe dynamic imports are the answer. This is just my theory on why I had to strictly seperate "use client" actions from "use server" actions.