chore: upgrade @types/eslint to v9
#94
Merged
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
snitin315
approved these changes
Jul 29, 2024
6 tasks
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.
Prerequisites checklist
What is the purpose of this pull request?
This PR upgrades
@types/eslintto the last version for ESLint v9.@types/eslintis only included indevDependencieswhich makes this change a chore, even if the eslint types are referenced in the published type declarations of@eslint/compatand@eslint/migrate-config.What changes did you make? (Give an overview)
@eslint/typesdependencies to"^9.6.0".compatpackage to work with both the v8 and v9 types.ConfigwithLegacyConfiginmigrate-configpackage to work with both the v8 and v9 types.coveragedirectories from linting with eslint.Related Issues
Is there anything you'd like reviewers to focus on?