chore: add ESLint configuration to catch code quality issues #549
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.
Summary
Adds comprehensive ESLint configuration to proactively catch common code quality issues that GitHub Copilot flags during PR reviews.
This is a preventive measure inspired by issues caught in #546, where Copilot identified several code quality concerns including type safety issues, promise handling, and unused variables during the ngrok migration review.
Changes
anytypes and unsafe type operationslint-stagedfor automatic checking on commitnpm run lintandnpm run lint:fixscriptsConfiguration Highlights
@typescript-eslintparser with type-aware lintinganyis sometimes needed)Testing
References
🤖 Generated with Claude Code