vuejs / eslint-plugin-vue-libs

Eslint plugin for Vue internal development

eslint-plugin-vue-libs

ESLint plugin for libs in the vuejs organization.

❗ Note this is an internal plugin/config for the development of Vue itself, not intended for Vue app development.

Usage

1. npm install eslint-plugin-vue-libs --save-dev
2. create a file named .eslintrc in your project:

{
  extends: ["plugin:vue-libs/recommended"],
  rules: {
    // override if necessary
  }
}

License

MIT

eslint-plugin-vue-libs's Issues

upgrade eslint-plugin-html

This plugin depends on eslint-plugin-html@2. However, it does not support ESLint 4. I want to upgrade it to latest. But it's a breaking change because the latest eslint-plugin-html supports only eslint@>=4.7.0.

Can we upgrade eslint-plugin-html to the latest?

[email protected] - Unable to resolve dependency tree

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: [email protected]
npm ERR! Found: [email protected]
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 [email protected]
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: [email protected]
Found: [email protected]
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 [email protected]
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

Use in conjunction with eslint-plugin-vue

I wanted to use this ruleset along with the eslint-plugin-vue, but cannot get them to work together. I get no output from running eslint.

This is what I have in the extends key of .eslintrc.json:

{
    "extends": [
        "plugin:vue/recommended",
        "plugin:vue-libs/recommended"
    ],
    ...
}

Switching order doesn't have any effect either, but if I copy the vue-libs ruleset and paste it directly in my .eslintrc.json rules array, then everything works as expected. Also, if I remove one or the other, it works, though I get a more limited set of rules than I intend to.

Am I doing something wrong?