PKG ERR! when extending eslint configs

I have the following .eslintrc in one of my projects:

{
  "extends": "touchlay",
  "env": {
    "node": true
  }
}

Additionally, I have eslint-config-touchlay installed and in package.json:

{
  ...
  "devDependencies": {
    ...
    "eslint-config-touchlay": "^0.2.2",
    ...
  }
}

eslint-config-touchlay has the plugins and other dependencies in its package.json, so they get installed correctly and linting works fine, however, running npm-check does not:

eslint-plugin-react              😟  PKG ERR!  Not in the package.json. Found in: /.eslintrc

eslint-config-standard           😟  PKG ERR!  Not in the package.json. Found in: /.eslintrc

eslint-config-plugin:import      😟  MISSING!  Not installed.
                                 😟  PKG ERR!  Not in the package.json. Found in: /.eslintrc
                                 ⛔️  NPM ERR!  Registry error Package `eslint-config-plugin:import` doesn't exist

eslint-plugin-standard           😟  PKG ERR!  Not in the package.json. Found in: /.eslintrc

eslint-plugin-promise            😟  PKG ERR!  Not in the package.json. Found in: /.eslintrc

Use npm-check -u for interactive update.

It also seems to have a problem (NPM ERR!) with eslint-config-plugin, which uses the following syntax to load the plugin via extends: "plugin:import/errors", "plugin:import/warnings"

[benjamine]

got this too:

eslint-config-plugin:react   😟  MISSING! Not installed.
                             😟  PKG ERR! Not in the package.json. Found in: /.eslintrc.json
                             ⛔  NPM ERR!  Registry error Package `eslint-config-plugin:react` doesn't exi

because my .eslintrc.json says:

{
  "extends": [
    "standard",
    "plugin:react/all"
  ]
}

and note that “plugin:react/all” actually comes from package named "eslint-plugin-react"

[rumpl]

Maintainer of depcheck here, surely the culprit for this issue.

Any chance that this will be considered to be fixed or not?

There is 100% chance it will be done if you open a PR yes.

I will take a look on my side and make a PR here to update the dependency