-
-
Notifications
You must be signed in to change notification settings - Fork 171
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
Invitation to move to official eslint-community
org
#341
Comments
This was referenced Sep 10, 2022
This was referenced Sep 21, 2022
@mysticatea Did you had the time to consider this? |
@mysticatea doesn't like to bother but friendly ping |
you might consider https://github.com/eslint-community/eslint-plugin-n/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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'seslint-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.The text was updated successfully, but these errors were encountered: