Supabase Auth Example #1830
Open
Supabase Auth Example #1830
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 failed. Why did it fail? →
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.