chore: remove unneeded type definitions and inline types for eslint-plugin-jsx-a11y
#406
Conversation
This file contains hidden or 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
G-Rath
requested review from
KristenEKelly,
PixeldroidAU,
eoinkelly,
hopkincame,
joshmcarthur,
justineleonard,
lukeify,
nzlaura,
robotdana,
simonchisnall-online and
stvmachine
nzlaura
approved these changes
Nov 21, 2025
simonchisnall-online
approved these changes
Nov 25, 2025
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.
The ones being removed have been upstreamed either by myself or others in the community; sadly the types for
eslint-plugin-jsx-a11yhave switched to using types fromeslintv9 rather than@types/eslintmeaning they cannot be used so long as we're supporting ESLint v8