Enhance ContributorsClient with Error Resilience Tests

[Shikhartiwari967]

Description

Fixes #6853

Changes

• Added ContributorsClient.error-resilience.test.tsx
• Verified rendering with valid contributor data
• Verified rendering with empty contributor data
• Verified Leaderboard renders correctly
• Verified ContributorsSearch renders correctly
• Verified Footer renders without runtime errors
• Added five isolated Vitest test cases

Pillar

• 🎨 Pillar 1 — New Theme Design
• 📐 Pillar 2 — Geometric SVG Improvement
• 🕐 Pillar 3 — Timezone Logic Optimization
• 🛠️ Other (Testing)

Visual Preview

N/A (Test-only changes)

Checklist before requesting a review:

• I have read the CONTRIBUTING.md file.
• I have tested these changes locally.
• I have run npm run lint locally.
• My commit follows the Conventional Commits format.
• I have updated README.md if required (not applicable).
• I have starred the repository.
• I have made sure I have only one commit in this PR.
• This PR only adds automated test coverage.

[vercel]

@Shikhartiwari967 is attempting to deploy a commit to the jhasourav07's projects Team on Vercel.

A member of the Team first needs to authorize it.

[retenta-bot]

This pull request introduces important error resilience tests for the ContributorsClient component, which is a great step towards improving the stability of our application. It aligns well with our previous decision to implement similar tests for the ContributorsSearch component, ensuring that we maintain a robust user experience even in the face of errors. Thank you for your contributions, and I look forward to your updates!

[github-actions]

🚨 Hey @Shikhartiwari967, the CI Pipeline is failing on this PR and it has been marked as status:blocked.

Please fix the issues before this can be reviewed. Here's how:

1. Run checks locally before pushing:

npm run format:check   # Check Prettier formatting
npm run lint           # Run ESLint
npm run typecheck      # TypeScript type check
npm run test           # Run unit tests (Vitest)
npm run build          # Verify production build passes

2. Auto-fix common issues:

npm run format         # Auto-fix formatting with Prettier
npm run lint -- --fix  # Auto-fix lint errors where possible

3. Check the full failure log here:
👉 View CI Run

Once you push a fix and the CI passes, the status:blocked label will be removed automatically. 💪

[Shikhartiwari967]

Hi @Aamod007 Sir,

I verified this test locally:

✅ npm test -- ContributorsClient.error-resilience.test.tsx passes (5/5 tests)
✅ ESLint passes for the new test file.

The CI failure appears to come from existing TypeScript errors in:

app/generator/components/EditorPanel.type-compiler.test.tsx
app/generator/components/PreviewPanel.type-compiler.test.tsx

These files are unrelated to the changes in this PR.

[Shikhartiwari967]

Hi @Aamod007 sir, review it.