Open
Conversation
…ling - Cache GitHub star count in localStorage with 1 hour TTL to reduce API calls - Add fallback star count used if API request fails (except abort errors) - Use ref to prevent multiple API fetches during component lifecycle - Handle fetch abort and errors more robustly with proper headers - Rename storage keys for clarity and avoid magic strings - Initialize star count state from cache on component mount - Improve code comments and error handling around localStorage usage
- Regenerated the tsconfig.tsbuildinfo to reflect recent build changes - Ensured build info is current for incremental TypeScript builds
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Description
Fixes the GitHub Star Banner to work reliably in production by implementing proper caching, error handling, and React best practices. The banner now gracefully handles API rate limits and network failures.
Related Issue
Closes #
Type of Change
Changes Made
160as fallback when API fails, ensuring banner always displaysuseRefto ensure single API call per sessionAccept: application/vnd.github.v3+jsonheader for GitHub APIHow Has This Been Tested?
pnpm test)pnpm typecheck)pnpm lint)Screenshots (if applicable)
N/A - No visual changes, only reliability improvements
Checklist