Notify big users of `eslint-plugin-node` that they may want to switch

[voxpelli]

It can be hard for users of eslint-plugin-node to find out that there's a maintained fork of the project.

I did a search to find out if some large projects were still relying on eslint-plugin-node and found out that yes, there indeed still are, so I created some PR:s to help them out:

• Replace eslint-plugin-node with maintained up to date community fork eslint-plugin-n webpack/webpack#17411
• chore: update ESLint related modules electron/electron#38874
• Koa (no PR yet)
• Motrix (no PR yet)
• Update linting to latest standard / prettier typicode/json-server#1445
• Use maintained fork of eslint-plugin-node emberjs/ember.js#20522
• Use correct standard peer dependencies github/docs#27425

[voxpelli]

Opened three new PR:s and updated the webpack one after feedback

[aladdin-add]

As of I'm writing, eslint-plugin-node, there is still 3M+ downloads per week in npm.

I was preparing a PR to renovate: renovatebot/renovate#26907. hope it helps.

[scagood]

I think we can probably class this as complete 🤔

Especially as the renovate PR is done (renovatebot/renovate#26907), and the original repo links here now (mysticatea#355)

[voxpelli]

I agree!