Resolving plugins in extended configs

[jancama2]

Versions

eslint@7.21.0

Situation

I have ESlint config in my project:

{
  extends: ['my-shared-config'],
  ...
}

my-shared-config is installed as a dependency in node_modules and look like this:

{
   plugins: ['react', 'react-hooks'],
}

and has dependecies in its package.json:

{
   "eslint-plugin-react": ...,
   "eslint-plugin-react-hooks": ...
}

With this configuration ESlint is not able to find eslint-plugin-react and eslint-plugin-react-hooks that are dependencies of my-shared-config and fails with the resolution error. For some reason the plugins are not being resolved from the my-shared-config inner node_modules but I have to explicitly install them in the project.

Question

Shouldn't the plugins that are the dependencies of my-shared-config and are installed along with the config be resolved from its inner node_modules the same way node module resolution works? Because the way it works now forces me to install every plugin that all the extended configs need explicitly in the project.

[jancama2]

If I understand the migration guide properly this even shouldnt happen in eslint@7 and plugins related to a certain config file should be resolved relative to it.

[jancama2]

But I guess it is correct behavior as the RFC for this implies and the important word in the afore mentioned migration guide is entry config file and all the plugins, even the ones from the extended configs, are resolved relative the the entry config file.

[jancama2]

#3458 issue implies the same as the RFC. So the answer is that all the plugins are resolved relative to the entry config (the config in the project) and it doesn't make sense to install plugins as dependencies of shareable configs as they won't be used. One of the reasons it works this ways is uniqueness of rules provided by a certain plugin in different versions.