ESLint Rule Suppressions in Production Code

[csxark]

Description

13 eslint-disable-next-line comments suppress legitimate warnings:

• react-hooks/exhaustive-deps in ChallengeMode.tsx (potential stale closures)
• react-hooks/set-state-in-effect in context.tsx, DailyQuiz.tsx
• @typescript-eslint/no-require-imports in profiler.ts, reporter.ts, baseline.ts (6 instances)

Affected Files

• components/challenge/ChallengeMode.tsx
• lib/i18n/context.tsx
• components/challenge/DailyQuiz.tsx
• lib/performance/profiler.ts
• lib/performance/reporter.ts
• lib/performance/baseline.ts

Proposed Solution

1. For exhaustive-deps: add missing deps or use ref-based patterns
2. For set-state-in-effect: restructure to avoid state setting in effects
3. For no-require-imports: migrate require() calls to dynamic import()
4. Document any suppressions that truly cannot be resolved

Acceptance Criteria

• Each suppression reviewed and either resolved or documented with justification
• exhaustive-deps suppressions eliminated
• Total suppression count reduced by ≥50%

[github-actions]

💙 Welcome Back

Hello @csxark,

Thank you for opening another issue and for your continued interest in contributing to CryptoViz.

We greatly appreciate your ongoing support and the time you invest in helping improve the project.

Your issue has been received and will be reviewed by the maintainers as soon as possible.

❤️ Support CryptoViz

If you find CryptoViz helpful, consider supporting the project by:

• ⭐ Starring the repository
• 🍴 Forking the repository
• 👤 Following Ark on GitHub
• 💼 Connecting on LinkedIn
• 🌐 Visiting the Portfolio

Your support helps increase the project's visibility and encourages continued development. Thank you for being a part of the CryptoViz community!

Thank you for being a valued member of the CryptoViz community. We look forward to collaborating with you again.

[Chigael]

@csxark I'd like to work on this as ECSoC26 contribution

[Kushal-prime]

/claim

[github-actions]

🎉 Issue Assigned

Hi @Chigael, this issue has been assigned to you. You have 3 days to work on it before it may be unassigned if no progress is made.

Thank you for your interest in contributing to the CryptoViz project. We appreciate your willingness to contribute and look forward to your work on this issue.

Before you begin

• Sync your fork with the latest main branch
• Pull the latest changes
• Create a new feature branch
• Implement the requested changes
• Test your implementation thoroughly
• Ensure all linting and build checks pass
• Reference this issue in your Pull Request

Keeping your fork up to date with the latest main branch before creating a feature branch helps minimize merge conflicts and streamlines the review process.

If you have any questions or need clarification while working on the issue, feel free to ask. We look forward to reviewing your contribution.