Repository navigation
fix: add missing Vite proxy entries for auth, users, history, debug routes - #11
Merged
Merged
Conversation
Root cause confirmed: Vite proxy was missing /auth entries. Debug panel no longer needed.
…s for first-admin check
…ettings page, roadmap
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
/auth,/users,/history, and/debugroutesfetch('/auth/status')in the Vite dev server returned<!DOCTYPE html>(SPA fallback) instead of JSON, causingauthRequiredto stayfalseand the app to appear always-logged-inRoot cause
vite.config.tsonly proxied/chat,/sessions, and/stats. The new RBAC routes (/auth,/users) and existing routes (/history,/debug) were missing, so all API calls to those paths duringnpm run devhit the Vite SPA fallback instead of FastAPI.Test plan
npm run devand navigate to the appJWT_SECRETis set in.env