How can I add plugins to eslint config ?

[p-l-l]

Hi, I am trying to add the react-hooks plugin to my custom env eslint config.
I did use Bit install to have the following depency "eslint-plugin-react-hooks": "4.2.0"

I am using this code to configure my linting rules in a custom env:

react.useEslint({
        transformers: [
          (config) => {
            config.addPlugins(['react-hooks']);
            config.setRule("react-hooks/rules-of-hooks", "error");
            config.setRule("react-hooks/exhaustive-deps", "warn");
           
            return config;
          },
        ],
      }),

Everything's been working fine (with other rules) until I used the config.addPlugins(['react-hooks']); line, which throws the
following error when using bit lint :

service linter env pll-org.design/extensions/custom-react has failed. Invalid Options:
- Unknown options: extends

Also made sure to bit build -> bit compile -> bit lint with the saved changes.

Is there any example on how a plugin can be added ? Am I missing a step ?

[GiladShoham]

It might be a bug. I'll check it with in a few days and will let you know

[p-l-l]

Hi @GiladShoham, been taking a break from my Bit project for a while, now I am back at it. I saw this interesting way of sharing eslint config from learn-bit-react and I made a config and was able to make it work in VS Code.
I am trying to reuse it in my custom env extension

react.useEslint({
  transformers: [
	(config) => {
		config.raw.config.baseConfig = eslintConfig;
		return config;
	},
  ],
}),

I still have trouble when it comes to extends and plugins

How do I provide the dependency (in this case eslint-config-react-app) ? I tried adding it to overrideDependencies as devDependencies, but still got the same error..

Thanks for any help!

[benjgil]

@p-l-l
I can't say whether this will solve your issue, but when it comes to your env the eslint packages are regular deps, not devDependencies - they are used in the core of the component, not just to develop it.
It's part of the mental shift to component-driven development. Once you can have components which themselves define the dev process, you then have situations where packages which are usually devDeps become regular dependencies.

So tl;dr - try adding them as regular dependencies