Deprecate Node-specific core rules

[kaicataldo]

The version of ESLint you are using.
master

The problem you want to solve.

The number of rules in core has grown to the point that we have to set a very high bar for new rules. To improve our ability to maintain core, I think it makes sense to treat the current core Node/CommonJS rules similarly to how we handled the deprecation of core JSDoc rules. I believe these are the last runtime/library specific rules that we have in core, and think this also makes sense for the sake of consistency.

Your take on the correct solution to problem.

As discussed in our TSC meeting (notes here), this proposal is to deprecate all the Node/CommonJS-specific rules in core and to move all of them into eslint-plugin-node, maintained by @mysticatea.

Are you willing to submit a pull request to implement this change?
Yes!

Questions

1. @mysticatea Are you still okay with this? Just wanted to check because it's been a little while since we last discussed this.

[mysticatea]

Thank you for this issue.

Are you still okay with this? Just wanted to check because it's been a little while since we last discussed this.

Yes!

[kaicataldo]

Marking as accepted since this was decided on during a TSC meeting and @mysticatea is still on board.

[kaicataldo]

I'll work on this :)

[kaicataldo]

Steps to complete this:

• Port rules over to eslint-plugin-node (Update: add ESLint core Node.js and CommonJS rules mysticatea/eslint-plugin-node#206)
• Deprecate rules in core (Update: deprecate Node.js & CommonJS rules #12898)
• Write a blog post similar to https://eslint.org/blog/2018/11/jsdoc-end-of-life

[ljharb]

I know it might be late, but this seems like a terrible idea. Having rules in core is paramount for discoverability, especially since shared configs and peer deps are still a huge PITA, until shared configs can bring along plugins as regular deps.