Personal config (~/.eslintrc) doesn't load global-installed configs/parsers/plugins

Tell us about your environment

• ESLint Version: 6.0.1
• Node Version: 12.4.0
• npm Version: 6.9.0

What parser (default, Babel-ESLint, etc.) are you using? default

Please show your full configuration:

Configuration

{
  "env": {
    "browser": true,
    "commonjs": true,
    "es6": true,
    "node": true
  },
  "extends": [
    "standard"
  ],
  "parserOptions": {
    "ecmaFeatures": {
      "jsx": true
    },
    "sourceType": "module"
  },
  "plugins": [
    "html",
    "css-in-js",
    "json"
  ],
  "rules": {
    "no-const-assign": "warn",
    "no-this-before-super": "warn",
    "no-undef": "warn",
    "no-unreachable": "warn",
    "no-unused-vars": "warn",
    "constructor-super": "warn",
    "valid-typeof": "warn"
  }
}

What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.

I updated eslint from version 5.16.0 to 6.0.1 and, since I did it, eslint failes to start and I always receive this error: ‘Failed to load config “standard” to extend from eslint 6’.

What did you expect to happen?

I expected that all worked fine.

[wintercounter]

I had enough of this and created the following package: https://github.com/wintercounter/eslint-global-patch

It is a very unsafe and ugly workaround, it’ll patch your ESLint installation. For my use case it works fine for all our projects.

[tonywoode]

my 2cents: I can’t upgrade eslint past v5, as ALE in Vim will report ‘Failed to load config “standard”’ - just as CLI does. I’ve read all issues here related to forcing users to stop using a global config, and I don’t agree for reasons already cited above in this ticket. I see no option open to me atm than to slowly die on v5? That does not seem reasonable