fix: enforce SUPABASE_URL and SUPABASE_SECRET_KEY presence in server-side client; remove unused supabase-server.ts file#138
Merged
Conversation
…side client; remove unused supabase-server.ts file
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Clean up Supabase environment handling and remove an unused frontend server-side Supabase helper.
Changes
frontend/src/lib/supabase-server.tshelper.SUPABASE_SECRET_KEYfrom the frontend env documentation.createServerSupabase()whenSUPABASE_URLorSUPABASE_SECRET_KEYis missing.Why
The frontend should not require or document the Supabase service-role key. Backend Supabase access should also fail clearly at startup/runtime instead of constructing a client with an empty URL or key.
Testing
npm run build --prefix backendnpm run build --prefix frontend