Fix blank packaged dashboard with runtime Supabase configuration - #85
Merged
Merged
Conversation
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.
Packaged dashboard builds without Vite Supabase variables crashed before rendering the login page. Serve public Supabase configuration from the backend before loading React, with build-time settings retained for standalone development.
Add configuration API coverage and a Chromium startup test to CI, update dashboard setup documentation, and release patch 0.13.2. Worker images remain v0.13.1; no schema changes.
Validation: 8 dashboard API tests pass, frontend builds without Vite settings, and the resulting login page renders in Chromium with no page errors. Production's immediate repair was also verified in Chromium.