-
Notifications
You must be signed in to change notification settings - Fork 394
feat: Supabase Auth Example #1830
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
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. |
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.