Extends doesn't work #87
Comments
I also came across this trying to extend airbnb's config.
I traced it down to eslint requiring the extension. Solutions that didn't work:
Hopefully someone has a more creative solution |
I use extends with https://github.com/ericclemmons/eslint-config-future and it's working great all I have is:
In my
What's different from me? |
I reproduced your setup in this gist and it worked great. The only differences were using a more stable version of |
I'm not using a eslint config module but just extending a config file like |
@AdriVanHoudt Working? |
not used Atom recently but I thought my last try of 1.0 did work yes, will test soon |
I'll close this so, just confirm me later or open new issue 👍 |
so quick test and it can't find all the rules (of a plugin), I know this is something difficult since I have debugged the same issue with the author of the eslint linter of brackets, would be really nice if eslint could provide debug info of where it is looking for the plugins/rules |
@AdriVanHoudt Could you provide me an easy repro case? |
Basic node server with lab testing lib of which I extend the eslint config and the server has a basic eslint config: {
"env": {
"node": true
},
"extends": "./node_modules/lab/lib/linters/eslint/.eslintrc",
"rules": {
"no-undef": 2
}
} |
Version 2.0 has been released now using CLI, please open a new issue if something is wrong. |
The 'new' extends function doesn't work properly with plugins. If a plugin is defined in the extended config, the linter can't seem to find it
The text was updated successfully, but these errors were encountered: