Replies: 1 comment 3 replies
-
The option is eslintrc-only, however, it's deprecated and feature-frozen. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
ESLint version
8.57.0
What problem do you want to solve?
ESLint currently has a
resolvePluginsRelativeTo
parameter in its constructor, but does not have aresolveConfigsRelativeTo
param.Why do I want this?
I have a monorepo with the current file structure:
I want to install
eslint
and all of its configs and plugins into therepotools/central-linter/node_modules
. I do not want to install a separate copy of eslint and its plugins in each app/package. Also note that there is nopackage.json
file at the root of the repo because I have lots of issues with npm workspaces.I also want to keep the
.eslintrc.json
and.eslintignore
files at the root of the monorepo for better IDE integration.I am able to accomplish all of this except for resolving the shared
eslint-config-*
modules, since they are still resolving relative to the repository root.What do you think is the correct solution?
Add a
resolveConfigsRelativeTo
that works the same way asresolvePluginsRelativeTo
for extending shared configs.Participation
Additional comments
No response
Beta Was this translation helpful? Give feedback.
All reactions