Repository navigation
Keep schedule in the prefetched App Shell (cacheLife stale 300s) - #8
Open
gellosparkles wants to merge 2 commits into
Open
gellosparkles wants to merge 2 commits into
gellosparkles wants to merge 2 commits into
Conversation
- getSchedule: raise cacheLife stale to 300s (revalidate stays 30s) so the schedule stays in the prefetched App Shell; stale < 5 min excluded it. - getCurrentUser: await connection() before Supabase getClaims(), which reads Date.now() to check token expiry. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
PR #7 landed the same await connection() change in src/lib/auth.ts, and the auto-merge duplicated the import and call. Keep main's version. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gellosparkles
changed the title
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
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.
What
Fixes the "uncached data during prerendering" warning on
/in the Next.js dev overlay.PR #6 set
getSchedule()tocacheLife({ stale: 30, ... }). WithcacheComponents+partialPrefetching, astaleunder 5 minutes drops the cache entry out of the prefetched App Shell, so the home page lost its instant navigation.staleis now 300;revalidatestays 30, so edits made straight in Supabase still reach the server within ~30s, and/adminedits still show immediately viaupdateTag("events").The
/profileDate.now()warning was also fixed here originally, but #7 landed the sameawait connection()change insrc/lib/auth.tsfirst, so this PR now keeps main's version and only changessrc/lib/data.ts.Testing
/,/people,/profilenpm run lint,npx tsc --noEmit,npm run buildpass on the branch merged with main🤖 Generated with Claude Code