Michaël De Boey

@greg-db I would be happy to contribute a PR for this, but as there's no API endpoint for it, I can't really do anything I'm afraid 🤔😕

@F3n67u Is this related to #199? 🤔

@weyert Like I said yesterday (https://github.com/mysticatea/eslint-plugin-node/pull/224#issuecomment-647456078): We still have to wait for mysticatea/eslint-utils#7 before we can start going forward with #224 🙂

@aladdin-add Would be nice if we could transfer repos like [`eslint-plugin-node`](https://github.com/mysticatea/eslint-plugin-node), [`eslint-plugin-es`](https://github.com/mysticatea/eslint-plugin-es), [`eslint-utils`](https://github.com/mysticatea/eslint-utils) & [`@mysticatea/eslint-plugin`](https://github.com/mysticatea/eslint-plugin) to a new @eslint-community org CC/ @mysticatea

Transferring them to the @standard org is fine for me too 🤷‍♂️ I just think we should transfer it to an org that will take care of maintenance long term,...

Let me know if I can help somehow!

@weyert We still have to wait for mysticatea/eslint-utils#7 before we can start going forward with this one 🙂

Since all tests are green for ESLint 7.x, I think we can merge this one without https://github.com/mysticatea/eslint-utils/pull/7 being merged 🙂

@mysticatea All tests are green (locally), so I think we can merge this one 🙂 CC/ @sosukesuzuki @ota-meshi

@voxpelli Most of the changes are due to updating `@mysticatea/eslint-plugin`. Would it help if I created separate commits in order to understand a bit better what's happening?