After several hours of trying to get this to work, I have to admit defeat and ask for help.
The error I am getting is:

I've tried all the suggestions in similar issues including only having the packages global, and only having the packages local. Neither works for me.
Currently, I have a local-only setup, which looks like this:





According to all the advice I've read here and elsewhere, this should be working. I must be not understanding something correctly. Any help would be greatly appreciated, thanks!
I think you need to specify the full name of the config, such as eslint-config-google.
Here's my eslint config, and this works (this is a _js_ file, not _json_, hence the module.exports)
/* .eslintrc.js */
module.exports = {
root: true, /* restrict to this level */
extends: [
"eslint-config-playlyfe",
"eslint-config-playlyfe/rules/testing",
],
plugins: [
"eslint-plugin-playlyfe",
],
.
.
.
};
@kumarharsh Thanks for the suggestion, but unfortunately that didn't seem to make a difference.
@hmmChase @kumarharsh This is a duplicate of #101
@caiges after reading the documentation referenced in the issue you linked, I was able to figure out a workable solution. I had to substitute the name of the config in .eslintrc.json file with the path to the actual configs index.js file.
so now my .eslintrc.json looks like this as opposed to my original above.

However, you will get another error because the google config includes a config within it called XO. So you go into /node_modules/eslint-config-google/index.js and change this:

to this:

and tada....

woo!...
Nice find, I'll give that a try. The current behavior still needs a fix as
it's out of line with the expectations users will have given the eslint
spec. I haven't looked into the fix yet but it shouldn't be too hard to
resolve.
On Sun, Jul 31, 2016 at 5:52 PM Chase [email protected] wrote:
@caiges https://github.com/caiges after reading the documentation
referenced in the issue you linked, I was able to figure out a workable
solution. I had to substitute the names of the config in .eslintrc.json
file with the path to the actuals configs index.js file.so now my .eslintrc.json looks like this as opposed to my original above.
[image: image]
https://cloud.githubusercontent.com/assets/10532835/17280505/4517a7f8-575f-11e6-978e-0f0eeae54eba.pngHowever, you will get another error because the google config includes a
config within it called XO. So you go into
/node_modules/eslint-config-google/index.js and change this:
[image: image]
https://cloud.githubusercontent.com/assets/10532835/17280543/f7794960-575f-11e6-837b-c5b13edc460c.pngto this:
[image: image]
https://cloud.githubusercontent.com/assets/10532835/17280561/396eaf72-5760-11e6-9c09-4f0dc6404e2e.pngand tada....
[image: image]
https://cloud.githubusercontent.com/assets/10532835/17280581/6beb852e-5760-11e6-9e25-1db5c84b6cc4.pngwoo!...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode-eslint/issues/105#issuecomment-236468017,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAcmP_dv5fEvCbFBfouDVtkPlGnMy-Hks5qbUNDgaJpZM4JYt9t
.
just to add some more info...
If you try to do this for plugins, you get this error:

because ESLint automatically prefixes "eslint-plugin-" on any plugin value so the path gets messed up, which makes the Airbnb and Standard configs unusable.
@hmmChase Solution works ! thanks !
@hmmChase Is this still broken for you after the 1.4 release? My extended configs appear to be working now.
@hmmChase Could you give this a try using the latest ESLint extension. If the problem still exists do you see the same behavior in a terminal ?
Closing since I haven't received any response. Please ping if you still think this is a problem.
still exists in the latest version of eslint & vscode
It works well for me. @awebdeveloper Can you post a reproducible project link to test?
I had the same issue and was using a similar solution to hmmChase's until I installed eslint-config-google globally, and used "extends": "google" in my config. For reference: https://github.com/google/eslint-config-google
Most helpful comment
I had the same issue and was using a similar solution to hmmChase's until I installed eslint-config-google globally, and used
"extends": "google"in my config. For reference: https://github.com/google/eslint-config-google