Fix duplicate data-layer calls during build#16986
Merged
Merged
Conversation
✅ Deploy Preview for ethereumorg ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
wackerow
approved these changes
Dec 27, 2025
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.

I noticed we were hitting Netlify Blobs multiple times for the same data during static generation. For example,
getGrowThePieDatawas being called 6 times instead of once when building the layer-2 pages.The issue: Next.js renders each page twice during build (data collection + HTML generation), and
unstable_cachealone doesn't deduplicate within the same render cycle.The fix: Wrap our cached getters with React's
cache()function, which memoizes calls within the same request/render. Now we get:cache()→ deduplication within same renderunstable_cache→ persistence across requests with time-based revalidationBefore: ~6 calls per data source during build
After: ~2 calls (one per worker process)