chore: Update typescript-eslint settings #20
Merged
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.
This pull request updates the ESLint configuration and related code to improve TypeScript support, enforce stricter linting rules, and fix minor issues. The most important changes are grouped below.
ESLint Configuration Improvements:
js.configs.recommendedtoeslint.configs.recommendedfor base ESLint configuration, ensuring better compatibility with the latest ESLint ecosystem.typescript-eslintparser and stricter rules, including enabling the@typescript-eslint/strict-boolean-expressionsrule for enhanced type safety../packages/*/tsconfig.jsonto./packages/**/tsconfig.jsonfor broader coverage.eslint-config-prettierdependency frompackage.jsonto clean up project dependencies.Code Quality and Bug Fixes:
getConfigby awaiting thepathExistscheck, ensuring correct config file resolution.no-unused-varswarning for the abstractactionmethod parameter inBase.ts, improving code clarity for future maintainers.