forked from mysticatea/eslint-plugin
-
-
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
Deprecate when moving to ESLint 9 #183
Comments
This issue has been automatically closed because we haven't received a response from the original author 🙈. This automation helps keep the issue tracker clean from issues that aren't actionable. Please reach out if you have more information for us! 🙂 |
The dependency web we currently have graph TD;
eslint-plugin-es-x-->eslint-plugin-n
eslint-plugin-eslint-comments-.->eslint-plugin-eslint-plugin
eslint-plugin-eslint-comments-.->eslint-plugin-es-x
eslint-plugin-mysticatea-.->eslint-plugin-eslint-comments
eslint-plugin-mysticatea-.->eslint-utils
eslint-plugin-mysticatea-.->regexpp
eslint-utils-->eslint-plugin-es-x
eslint-utils-->eslint-plugin-eslint-plugin
eslint-utils-->eslint-plugin-n
regexpp-->eslint-plugin-es-x
Legenda:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think we should strive to move the few of the
eslint-community
modules that uses this plugin off from it rather than upgrade this one to ESLint 9.A code search gives this list of modules:
What we should do is to just have a reusable config instead, eg:
@eslint-community/eslint-config
Could probably make it similar to https://github.com/neostandard/neostandard (which I was part of creating on top of ESLint 9)
The text was updated successfully, but these errors were encountered: