chore: upgrade to typescript-eslint v8 #5478
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Which problem is this PR solving?
The repository currently depends on an old version of typescript-eslint (v5).
Short description of the changes
Upgrading to typescript-eslint v8 to pick up the latest recommended lint rules and modifying the code to be compliant with the new rules. In most cases, this required updating/adding new ignores for renamed/new rules. In other cases, non-breaking changes were made to the code to make it compliant. I also upgraded
eslintto the last v8 version due to a new stricter peer dependency requirement.How Has This Been Tested?
npm run lintandnpm run testsucceed.