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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
looking for maintainers? #300
Comments
馃憤 Same here, would love to help out to ensure that this stays up to date and can continue to support https://github.com/standard/standard |
for someone blocked by the plugin, I've just pushed a fork:
it just added supports for eslint v8. |
@aladdin-add add a link to the github repo rather than the npm link, in your above post? |
updated. 馃帀 |
Since eslint-plugin-node has been dormant for quite a while: mysticatea/eslint-plugin-node#294 mysticatea/eslint-plugin-node#300 eslint-plugin-n is an actively maintained fork which is used by xo: xojs/xo#660 switch to that fork. Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
Let's hope we can transfer the original repo asap to the new @eslint-community org 馃檹 See #341 |
eslint-plugin-node is not maintained anymore mysticatea/eslint-plugin-node#300
`eslint-plugin-node` is not maintained anymore mysticatea/eslint-plugin-node#300
it was forked from eslint-plugin-node v11.1.0. as the original repository seems no longer maintained. repo link: github.com/eslint-community/eslint-plugin-n npm link: https://www.npmjs.com/package/eslint-plugin-n related discussion: mysticatea/eslint-plugin-node#300
it was forked from eslint-plugin-node v11.1.0. as the original repository seems no longer maintained. repo link: github.com/eslint-community/eslint-plugin-n npm link: https://www.npmjs.com/package/eslint-plugin-n related discussion: mysticatea/eslint-plugin-node#300
it was forked from eslint-plugin-node v11.1.0. as the original repository seems no longer maintained. repo link: github.com/eslint-community/eslint-plugin-n npm link: https://www.npmjs.com/package/eslint-plugin-n related discussion: mysticatea/eslint-plugin-node#300
I'm happy to help! 馃檶
The text was updated successfully, but these errors were encountered: