Global Installs with ESLint 7 / couldn't find the config "wesbos" to extend from

[theBhavikJoshi]

Trying to install but facing this error.

ESLint couldn't find the config "wesbos" to extend from. Please check that the name of the config is correct.
The config "wesbos" was referenced from the config file in "~/.eslintrc".

[Asjas]

@theBhavikJoshi Can you try installing the latest version of eslint-config-wesbos and see if you get the same error message? 🙂

There was an error being thrown due to an out-of-date package which caused that failed to find the config "wesbos" error. I just tested using the latest release of Wes's plugin and it's now fixed.

[theBhavikJoshi]

@Asjas thanks for your reply.
I have tried installing the latest version and still facing the same issue.

[Asjas]

Can you post the contents of your package.json file here?

[theBhavikJoshi]

I am trying to install this globally on my system. It should work globally, right?

[Asjas]

There are instructions in the Readme on how to set it up globally so yeah, it should work 🙂

[theBhavikJoshi]

Yes, exactly. I followed the instructions to set it up globally but it isn't working in my case.

[Asjas]

Are you using a node version manager such as n or nvm? Or you do you Node.js directly installed on your system?

I can reproduce the error when I use n to manage my Node version.

[theBhavikJoshi]

@Asjas yes, I am using a node version manager, nvm. Any workaround for this?

[itstheandre]

Hey @Asjas is there a way around the nvm issue?

I am also seeing the sam eissue on my computer

[johnbburk]

I'm also seeing the same issue on a global install, even after following the steps to delete everything and try reinstalling.

[daveholst]

I'm having the same problem with a global install. I don't believe I have a node version manager installed.

[svikas641]

Hi Everyone, who's facing the issue in global installation including me. After a bit of research i found this i don't know how much true this is, if anyone knows please clarify, Thanks.

[itstheandre]

After a lot of research I also found that. So I guess that Wes's setup wont break amazingly if we dont have an .eslintrc in the root of every project, I guess prettier wont be doing anything, because we disabled everything, right?

[Asjas]

I'm not getting the global eslint working and I can get the local installation working immediately. I'd personally suggest setting up this eslint-config locally per project, that is how I personally use eslint.

For the most part it appears that eslint is deprecating the global installation and recommends that eslint be installed locally per project. jsx-eslint/eslint-plugin-react#2339 (comment)

People have been recommending to try either eslint . --resolve-plugins-relative-to="global_node_modules_dir" in the CLI or to set up vscode-eslint with the following settings in the settings.json file to resolve the eslint plugins globally but I haven't gotten that working.

"eslint.options": {
  "resolvePluginsRelativeTo": "global_node_modules_dir"
},

[itstheandre]

I wonder if there is a way to conditionally run the paths. something like: check current folder, check above until it eventually finds the one on the root folder

[wesbos]

Shoot eh - I like having an eslint globally because not every .js file I write is a huge project...

[wesbos]

I made an issue on the git repo to see if there is a solution for doing something like this.

[stefansdev]

I'm facing this issue on gatsby new starter. Working globally with nextjs and everything else, just in gatsby doesnt.

[wesbos]

Global installs do not work anymore. Sorry folks!

[jeremyarrabe]

After a lot of research I also found that. So I guess that Wes's setup wont break amazingly if we dont have an .eslintrc in the root of every project, I guess prettier wont be doing anything, because we disabled everything, right?

Is there any work around on this?

[Asjas]

@jeremeheh Can you expand on your question? 🙂

[SerhatTeker]

Global installs do not work anymore. Sorry folks!

I think we should update README according to this then. "No global install anymore"