Do not require modules with shareable config to be named eslint-config-*
See original GitHub issueIn our team we use eslint with a bunch of projects. Naturally we want to use the same eslint configuration in our projects. To do that we have created a separate package with the shared .eslintrc. We include it as dev dependency in our projects and pass its .eslintrc on the command line via -c option.
This works but then we found that we cannot use local .eslintrc files to extend/override the shared configuration.
Now I have found Shareable Configs which is a great idea. Unfortunately it requires that “the module name begins with eslint-config-
”. This seems rather restrictive. To use it, we would have to rename our package with shared config, which would be a breaking change.
Why not make this an optional prefix? For example if we have
extends: xyz
Then search for package:
- eslint-config-xyz
- xyz
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:10 (7 by maintainers)
Also it breaks everyone who use one repo for all linters (not only for eslint) in the same repo. Plus it actually breaks the nodejs resolution which is a bad practice in the first place.
@not-an-aardvark it’d be nice if when a path to a specific file was provided, the prefix wasn’t added. Specifically,
package/path/to/file.js
.