feat(core): wrap layout-level guest queries in unstable_cache#2978
Open
feat(core): wrap layout-level guest queries in unstable_cache#2978
Conversation
🦋 Changeset detectedLatest commit: 63aafa4 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Bundle Size ReportComparing against baseline from No bundle size changes detected. |
Contributor
Unlighthouse Performance Comparison — VercelComparing PR preview deployment Unlighthouse scores vs production Unlighthouse scores. Summary ScoreAggregate score across all categories as reported by Unlighthouse.
Category Scores
Core Web Vitals
|
ed4e6ad to
a45174e
Compare
a45174e to
f1f3c64
Compare
f1f3c64 to
87c2826
Compare
87c2826 to
185ba5a
Compare
185ba5a to
bad2bf4
Compare
…equest Add optional locale parameter to client.fetch() for use in cached contexts. Wrap headers() call in beforeRequest with try/catch so it gracefully degrades inside unstable_cache. No changes to getChannelId or beforeRequest callback signatures. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Wrap home page, header, footer, SEO canonical, reCAPTCHA, and root layout metadata queries in unstable_cache for guest visitors. Authenticated requests continue to bypass the cache with no-store. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
bad2bf4 to
63aafa4
Compare
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.
Linear: LTRAC-226
What/Why?
Wraps shared layout-level data-fetching functions in
unstable_cachefor guest (unauthenticated) visitors. This caches the return values server-side with a configurable revalidation interval, reducing redundant GraphQL calls for anonymous traffic.Functions migrated:
getPageData(home page)fetchRootLayoutMetadata(root layout)getHeaderData,getHeaderLinks(header)getFooterData,getFooterSections(footer)getVanityUrl(SEO canonical)getReCaptchaSettings(reCAPTCHA)Authenticated requests continue to bypass the cache entirely (
cache: 'no-store').Third in a series of PRs splitting #2910. Depends on #2977.
Rollout/Rollback
No feature flag. Rollback is a simple revert. Cache revalidation interval is controlled by
DEFAULT_REVALIDATE_TARGETenv var (defaults to 3600s).Testing
pnpm buildpassespnpm lintpasses🤖 Generated with Claude Code