vuetifyjs / eslint-plugin-vuetify

An eslint plugin for Vuetify

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Does not work with eslint v7 without --legacy-peer-deps

l3d00m opened this issue · comments

(follow-up of #26)

Installing this plugin with "eslint": "^7.22.0" in my package.json fails with the following output:

> npm install eslint-plugin-vuetify --save-dev              
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! Found: eslint@7.22.0
npm ERR! node_modules/eslint
npm ERR!   peer eslint@">= 4.12.1" from babel-eslint@10.1.0
npm ERR!   node_modules/babel-eslint
npm ERR!     dev babel-eslint@"^10.1.0" from the root project
npm ERR!   peer eslint@"^7.12.1" from eslint-config-standard@16.0.2
npm ERR!   node_modules/eslint-config-standard
npm ERR!     dev eslint-config-standard@"^16.0.2" from the root project
npm ERR!   8 more (eslint-loader, eslint-plugin-es, eslint-plugin-import, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^5.0.0 || ^6.0.0" from eslint-plugin-vue@6.2.2
npm ERR! node_modules/eslint-plugin-vuetify/node_modules/eslint-plugin-vue
npm ERR!   eslint-plugin-vue@"^6.2.2" from eslint-plugin-vuetify@1.0.0-beta.8
npm ERR!   node_modules/eslint-plugin-vuetify
npm ERR!     dev eslint-plugin-vuetify@"*" 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.
npm ERR! 
npm ERR! See /home/thomas/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/thomas/.npm/_logs/2021-03-15T18_11_31_166Z-debug.log

Which is probably due to this peer dependency (not sure what it is, I'm new to the node world). That peer dependency requires eslint v6

"eslint-plugin-vue": "^6.2.2",

It only works successfull if I install it with npm install eslint-plugin-vuetify --save-dev --legacy-peer-deps

npm version: 7.5.2
node version: v14.15.4

Just run into the same issue.