Add a way to disable a plugin

The version of ESLint you are using.

v7.17.0

The problem you want to solve.

Disable a plugin in a shareable config.

Your take on the correct solution to problem.

Native support for the equivalent functionality of https://www.npmjs.com/package/eslint-plugin-disable.

e.g.

{
  "plugins": ["react", "disable"],
  "processor": "disable/disable",
  "overrides": [
    {
      "files": ["tests/**/*.test.js"],
      "settings": {
        "disable/plugins": ["react"]
      }
    }
  ]
}

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

No.

CC @mradionov

[nzakas]

TSC Summary: This proposal seeks a way to disable a plugin that has been included by a shared config. Essentially, a way to say “I want the shared config except for this plugin it’s including.” Disabling the plugin would mean disabling all rules, unregistering processors, removing environments, etc.

TSC Question: Shall we accept this proposal?

[nzakas]

Okay, thanks for the clarification. I’m still not seeing a clear use case for disabling a plugin. If a shared config is using a plugin you don’t want, it seems like that’s not the right config to extend from. Configs aren’t meant to be infinitely configurable, and were designed specifically to override or add, not to delete.

Maybe someone else on the team feels differently, but I’m not in favor of this.