[feature request] Add support for .eslintrc directory

[ctjlewis]

The version of ESLint you are using.
latest

The problem you want to solve.
I want to be able to store an eslint config as its own standalone git repository, so it can be added to other repositories with git submodule add and managed independently. Git repos must be folders.

Your take on the correct solution to problem.
.eslintrc check for a directory ./ should also detect a .eslint/ or .eslintrc/ directory, and then use the default .eslintrc* logic to select a config .eslintrc* in that folder and apply it with respect to the parent folder ./.

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

[anikethsaha]

Thanks for the issue.

Though this is not 100% what you are looking for, maybe --config can be helpful like give --config .eslintrc/.eslintrc but it won't work completely as you want.

so about the proposal, this an interesting one, I have seen many tools supporting this. It would be helpful for a better project structure.

You need to submit an RFC for detailed design. But we can discuss here about the interest and queries from others.

[aladdin-add]

to clarify:

• eslint <7.0 does ignores .* files by default
• as of eslint v7.0, it does not ignore .eslintrc* by default

and, it will be changed in eslint v8, as you expected. :)

previous discussion:

• do not ignore files started with . by default #10341
• New: Do not exclude dot files by default rfcs#55
• Config File Simplification rfcs#9

[aladdin-add]

atm, you can add a !.eslintrc/ in your .eslintignore

[kaicataldo]

I don't think core should support this, as there are a few ways to achieve this already:

1. Putting a standard config file in the project root that extends the shared config in the Git submodule. This is how shared configs installed via npm also work.
2. Using the --config CLI flag.

[aladdin-add]

emm.. I've misread the issue somehow, please disregard my comment. 🤣

[ctjlewis]

Hey everyone, thank you for your comments and suggested workarounds.

This definitely isn't a needed feature, I would just find it super convenient to add my ESLint config to repos with version control using git submodule add. This could be extended further with GitHub templates so that setup involves zero steps as long as you have a global install of ESLint active via npm i -g eslint. Atm, I don't see a way of setting up config without publishing it to NPM or manually copying it over to each new project.

Admittedly, I dream of a day when Travis, NPM, and Git all respect a dot folder called .config/ so everyone doesn't have 18 dotfiles piling up in root (.eslintrc, .travis.yml, .npmignore, .gitignore, Rollup configs, Webpack configs, etc.).

[mdjermanovic]

extends can accept relative paths. Config file in a project could be as simple as:

{
  "extends": ["./.eslint/.eslintrc"]
}

[eslint-deprecated]

Unfortunately, it looks like there wasn't enough interest from the team
or community to implement this change. While we wish we'd be able to
accommodate everyone's requests, we do need to prioritize. We've found
that issues failing to reach accepted status after 21 days tend to
never be accepted, and as such, we close those issues.
This doesn't mean the idea isn't interesting or useful, just that it's
not something the team can commit to.

Thanks for contributing to ESLint and we appreciate your understanding.