Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Eslint@7.20.0 - Unable to resolve dependency tree #13

Open
webdevnerdstuff opened this issue Feb 22, 2021 · 2 comments
Open

Eslint@7.20.0 - Unable to resolve dependency tree #13

webdevnerdstuff opened this issue Feb 22, 2021 · 2 comments

Comments

@webdevnerdstuff
Copy link

Issue:
After updating to eslint 7.20.0 installing eslint-plugin-vue-libs will not install due to dependency tree.

Error:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: site@0.0.1
npm ERR! Found: eslint@7.20.0
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"^7.20.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^5.11.1 || ^6.0.0" from eslint-plugin-vue-libs@4.0.0
npm ERR! node_modules/eslint-plugin-vue-libs
npm ERR!   dev eslint-plugin-vue-libs@"^4.0.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Here is the full report:

# npm resolution error report

2021-02-22T18:21:00.513Z

While resolving: site@0.0.1
Found: eslint@7.20.0
node_modules/eslint
  dev eslint@"^7.20.0" from the root project

Could not resolve dependency:
peer eslint@"^5.11.1 || ^6.0.0" from eslint-plugin-vue-libs@4.0.0
node_modules/eslint-plugin-vue-libs
  dev eslint-plugin-vue-libs@"^4.0.0" from the root project

Fix the upstream dependency conflict, or retry
this command with --force, or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.

Raw JSON explanation object:

{
  "code": "ERESOLVE",
  "current": {
    "name": "eslint",
    "version": "7.20.0",
    "whileInstalling": {
      "name": "site",
      "version": "0.0.1",
      "path": "[removed]"
    },
    "location": "node_modules/eslint",
    "dependents": [
      {
        "type": "dev",
        "name": "eslint",
        "spec": "^7.20.0",
        "from": {
          "location": "[removed]"
        }
      }
    ]
  },
  "edge": {
    "type": "peer",
    "name": "eslint",
    "spec": "^5.11.1 || ^6.0.0",
    "error": "INVALID",
    "from": {
      "name": "eslint-plugin-vue-libs",
      "version": "4.0.0",
      "whileInstalling": {
        "name": "site",
        "version": "0.0.1",
        "path": "[removed]"
      },
      "location": "node_modules/eslint-plugin-vue-libs",
      "dependents": [
        {
          "type": "dev",
          "name": "eslint-plugin-vue-libs",
          "spec": "^4.0.0",
          "from": {
            "location": "[removed]"
          }
        }
      ]
    }
  },
  "peerConflict": null,
  "strictPeerDeps": false,
  "force": false
}

Solution:
Please update to support eslint 7.20.0

@cadenzah
Copy link

cadenzah commented May 1, 2021

Same issue. I configured ESLint using vue-loader and typescript and I got this problem.
+When I lint my project, it shows this error message:

ERROR in Failed to load plugin 'vue-libs' declared in 'node_modules/vue-loader/.eslintrc.js': Cannot find module 'eslint-plugin-vue-libs'
Require stack:
- /Users/cadenzah/Programming/JavaScript/log-analysis-tool/node_modules/vue-loader/__placeholder__.js
Referenced from: /Users/cadenzah/Programming/JavaScript/log-analysis-tool/node_modules/vue-loader/.eslintrc.js

FYI, I was using vue-loader with v15.9.6, and eslint with v7.25.0. It turned out that if I update my vue-loader to v16.1.2, the error above is fixed but my project does not execute properly, because my Vue application is with v2.7.

@cadenzah
Copy link

cadenzah commented May 1, 2021

+) If I install eslint-plugin-vue-libs anyway using --legacy-peer-deps option, it is installed and linting works normally, but it doesn't seem okay to install the plugin with force option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants