Open 43081j opened 8 months ago
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.
@43081j Any news on the fork?
Unfortunately not, I haven't had much time recently to look
If anyone wants to help, I'm happy to help set the package up etc (under es-tooling probably) and Collab
I'll ask around in discord too
@43081j I'm happy to help out where I can, but not sure if I can spend enough time to make the lib fully up-to-date tbh
@MichaelDeBoey are you on the e18e discord? (chat.e18e.dev)
I'll at least create the empty repo and write up a rough spec, then maybe a couple of us can share the load to at least get it off the ground. contributions will come once we have a first cut at least
@43081j I am! I've send you a friend request, so you can talk to me over there if you want.
I'll at least create the empty repo and write up a rough spec
I would start by forking the original repo tbh
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