Fix: Frontend 404 and React warnings #1046
Open
+23
−7
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
- Add empty page.tsx at root route to prevent 404 flash before middleware redirect - Fix React Fragment warning by using explicit conditional rendering for PlausibleProvider - Improves user experience during initial page load
|
@Alexbeav is attempting to deploy a commit to the Listinai Team on Vercel. A member of the Team first needs to authorize it. |
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.
🐛 Fix: Frontend 404 and React warnings
Problem
/) shows 404 before middleware redirect executesSolution
page.tsxat(app)/(site)/route to prevent 404 flashChanges
apps/frontend/src/app/(app)/(site)/page.tsx(NEW FILE)apps/frontend/src/app/(app)/layout.tsx(refactored lines 35-114)Testing
Breaking Changes
None - pure improvements, backward compatible
Why This Matters