-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ESLint couldn't determine the plugin uniquely. #13385
Comments
Similar issue. My app/ creates scaffolding (e.g. downstream) as part of an integration test.
adding |
@MaximeBernard ESLint loads all config files from the ancestor directories of lint target files. Then, ESLint 7.x loads plugins from the location of each config file which has the In your case, I guess it's solved if you add (currently, it loads |
Works perfectly, thank you @mysticatea 👍 |
May I suggest to add some documentation about this in https://eslint.org/docs/developer-guide/shareable-configs ? |
PRs to update documentation are welcome! |
To be honest, I thought about it but I don't fully understand how it works so I don't feel like the right person to do it... Or maybe you could point me to the right direction (the part in the code that handle that |
on 7.2.0 package "import" has conflicts, and is not working specifying root in eslinrc.js I could fixing with |
I'm trying to upgrade to eslint@7.1.0 but some breaking changes in the plugin resolution seems to get in the way.
I'm using a monorepo with yarn workspaces and the noHoist setting.
My current tree looks like this
but when I run
yarn workspace app lint
My packages .eslintrc configuration files are just
which are supposed to help us load specific plugins per package (i.e. eslint-plugin-react for app, not for api)
Any idea where to go from here?
I posted my issue on Gitter and someone suggested to use
--resolve-plugins-relative-to
but so far,eslint --resolve-plugins-relative-to ./packages/app src/**.ts*
andeslint --resolve-plugins-relative-to ./packages/app src/**.ts*
still look in the ROOTnode_modules
. Am I missing something?Bonus question for my curiosity: why eslint@7 wants uniqueness so badly?
Tell us about your environment
6.8.0
7.0.0
&7.1.0
Please show your full configuration:
Root .eslintrc
Children .eslintrc
``` { "extends": ["../../.eslintrc"] } ```The text was updated successfully, but these errors were encountered: