-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
eslint-plugin-jsx-a11y #21
Comments
FYI i have started this, but pulled a long thread where i also modernised most of the repo. Once my branch reaches a point where it builds, passes, etc, i'll push to a fork and mention here |
Is https://github.com/eslinter/eslint-plugin-jsx suitable for the alternative fork? |
given how many rules there are in the jsx-eslint plugin, it may be easier to just fork it tbh i haven't had time to finish the branch off recently but i'll try get to that soon. at least then maybe you can help me decide if we should push ahead with it or not if we can keep all the same compatibility, same rules, etc but drop the outdated dependencies - i think that would be ideal |
Oh, I mean to develop an absolutely independent eslint plugin while just reuse the plugin name. |
this plugin can be found here:
https://github.com/jsx-eslint/eslint-plugin-jsx-a11y
the maintainers will not want to remove the polyfill-like dependencies, so we have to fork.
if we manage to create a lighter fork, we should aim to migrate:
and more. but we can open separate issues for those once we have a viable fork
The text was updated successfully, but these errors were encountered: