[BUG] Fix React Hook Dependency Regressions and Linter Warnings
- Dominant language
- TypeScript
- Stars
- 716
- Forks
- 1.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 35
Description
### Describe the bug.
I have identified several ESLint exhaustive-deps violations across the codebase that could lead to stale state or memory leaks. These issues are currently triggering build-time warnings and should be rectified to ensure hook stability.
### Expected behavior
React hooks should have accurate dependency arrays to prevent runtime logic errors
### Screenshots
### How to Reproduce
Run the project linters using `npm run lint`
### 🖥️ Device Information [optional]
_No response_
### 👀 Have you checked for similar open issues?
- [x] I checked and didn't find similar issue
### 🏢 Have you read the Contributing Guidelines?
- [x] I have read the [Contributing Guidelines](https://github.com/asyncapi/.github/blob/master/CONTRIBUTING.md)
### Are you willing to work on this issue ?
Yes I am willing to submit a PR!
Contributor guide
Research direction
Start by running `npm run lint` and review the reported React exhaustive-deps violations across the codebase. Identify each affected hook and update its dependency handling so the warnings are resolved without stale state or memory-leak risks. Done means the lint command completes without these warnings and the hooks have accurate dependency arrays.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, react, typescript
- Domain
- frontend, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100