Plugin is no longer being maintained

[G-Rath]

This package has not received any human activity in years, though the bots continue to land dependency updates (including ones that are not actually correct).

This is sad in my eyes as I think there is value in Vue having an a11y plugin, and this particular package was born from the original becoming unmaintained - if there are any maintainers around that see this, I've been an active maintainer and contributor to ESLint plugins (including eslint-plugin-jest) and open source in general for a while, and would be happy to help with the maintenance so please feel free to reach out.

While there is already at least peer dependency issue, with the release of ESLint v10 which is not allowed by the defined range, this package will not be usable with NPM v7+

[vhoyer]

well, I have permissions to do release on npm and write on repo, but not to include you into the collaborator list, I'm sad myself, not to be able to properly maintain this repo, but I was burnt out for a little while there and then, since around a year-or-more ago, I've been not too active in the Vue ecosystem, so but if you are up to solving the issues here, or do stuff on your own, I'd be happy to help you get your stuff merged and released, at least until we get attention from the ppl with the correct permissions :)

If at any time you feel you want to reach out too me, I'm more than available through contact@vhoyer.dev (where I'll probably reply the quickest)

[vhoyer]

I see you have a draft opened, if you want to go ahead with it

[G-Rath]

@vhoyer thanks, the burn out gets very real and that is totally understandable :)

I've opened a few PRs around CI to get the ball rolling - ideally it'd be great if #1456 could get merged ASAP so that my PRs no longer require manual approval for CI to run, which'll make it a lot easier for me to get other PRs up that are ready to be merged. (you did that as I was typing this out 😄)

I think the first priority should be ensuring what is currently on main is green and getting a new release out since there's been a lot of dependency PRs automatically merged most of which are hopefully fine but I know vue-eslint-parser will need to be downgraded - the CI PRs I'm doing should help with that.

After that I'll have a look at what fixes I can do and in getting ESLint v10 support sorted.

I suspect it might very quickly be worth doing a new major to drop versions of Node and ESLint, but we can see how it looks after some of the above has been progressed

[vhoyer]

thank you so much for your work 💖

[rlorenzo]

@G-Rath, let me know if there is any way I can help. I was also looking to upgrade to ESLint v1.0, but was blocked by this dependency.

[G-Rath]

@rlorenzo thanks, though I think we're pretty much ready for a new release which'll have v10 support - ideally we should land #1472, #1475, and #1265 first though.

@vhoyer feel free to do a release when you've next got the bandwidth.

I have also had a look over some of the other issues and will likely some of them up depending on how some other things go, but nothing jumped out as particularly urgent or breaking and not having some level of contributor access will make it a lot harder to help out day-to-day.

At some point I might try to reach out to the other folks on @vue-a11y to see if we can get that changed especially if they're not active themselves - no promises, but right now at work we've got some projects on around building accessibility tools for govt and the like that I think would align very nicely with this pugin, so hopefully I'll be back in a few months with experts in the field to give advice on rules and settings and so on🤞

In the meantime I'm very happy to be pinged on stuff and to continue helping out where I can - I can promise I'll always be up for helping maintain dependency compatibility like with ESLint and Node majors, so long there's someone like @vhoyer around to do the merging and releasing 🙂

[vhoyer]

hey @kddnewton last time you did add me to the permissions, could you do it again? haha

[vhoyer]

meanwhile @G-Rath if you could share with us your npm username for eventually add it in the permissions

[G-Rath]

it's the same as my GH username 🙂