[6.7] running eslint through npm script throws error.

I don’t experience the issue when using eslint v6.6.x.

I have the following script in my package.json:

  "scripts": {
    "lint": "eslint ."
  },

If I run eslint . directly in the console it works correctly, but when I run npm run lint, it throws an error. It seems like it’s using the wrong config?

ESLint: 6.7.1.

ESLint couldn't find the config "adpyke-es6" to extend from. Please check that the name of the config is correct.

The config "adpyke-es6" was referenced from the config file in "C:\Users\pykea\.eslintrc".

If you still have problems, please stop by https://gitter.im/eslint/eslint to chat with the team.

[mysticatea]

Side note: As you may know, we have deprecated the config files in HOME directory. The error of this issue looks like thrown from unused config files in HOME directory (because it should not work since ESLint 6.0.0, I guess that you have not used it while a time), therefore I’d like to recommend to remove it.

[mysticatea]

Ah, OK, I have found what it happens. Thank you for providing the information.

This happens under the following conditions:

1. You have ESLint config in your HOME directory, but the config doesn’t work because of lacking dependencies in your HOME directory. (this behavior has been same since 6.0.0)
2. You have ESLint config in your project directory as well and it works well.
3. You started linting with the project directory itself (i.e., eslint .).

In the situation, first, ESLint has checked if the directory is ignored or not. Previously this process loads only .eslintignore. But since 6.7.0, this process additionally loads config files from the directory that the project directory exists because it uses ignorePatterns property of config files. If config files were not found in the directory that the project directory exists, it loads the config file in the HOME directory.

I think it’s not intuitive if eslint . command loads config files from outside of the project directory.