https://github.com/mysticatea/eslint-plugin-node

[thernstig]

Hi @mysticatea

I have found no other way to reach out to you, so I felt urged to try here. I apologize beforehand as I know this is not the repository for this, but I know of no other way to reach you.

https://github.com/mysticatea/eslint-plugin-node seems to have been abandoned. Is there any way you could make an announcement in the repository looking for new maintainers or similar?

I am confident most of the community is appreciative what you have done so far and wants the project to live on.

[MichaelDeBoey]

We're wanting to take over ownership as well with the new official ESLint community org

We would love to have this repo added to the official @eslint-community organization on GitHub.

As you can read in the '@eslint-community GitHub organization' RFC, the goal of this new org is to have a place where community members can help ensure widely depended upon ESLint related packages stay up to date with newer ESLint releases and doesn't hold the wider community back without depending on one person's GitHub/npm account.

Since this plugin is really popular (3M+ download/week), it's recommended because of the deprecation of some rules in ESLint v7, it's (together with eslint-plugin-eslint-plugin) a recommended plugin for linting custom plugins & since it's currently unmaintained (people are switching to using @weiran-zsd's eslint-plugin-n fork in the wider community, just like the main ESLint repo has done: eslint/eslint#16150), we'd love you —@mysticatea— to transfer this repo to a better home, so you're welcome to transfer this repository to the new org.

mysticatea/eslint-plugin-node#341

---

@thernstig New commits to this repo are auto-generated btw, so I think @mysticatea won't answer here neither unfortunately 😢