Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Maybe not compatible with ESLint@4.4.0

See original GitHub issue

Tell us about your environment

ESLint Version: 4.4.0
eslint-plugin-vue Version: 3.10.0
Node Version: 8.2.1

Please show your full configuration:

.eslintrc.js:

module.exports = {
  root: true,
  extends: [ '../eslint-config-riophae/vue.js' ], // https://github.com/riophae/eslint-config-riophae/blob/24da6bb3723e60e8721075db7baccfc0a6c12bdd/vue.js
  rules: {
    indent: 0,
    'prefer-destructuring': 0,
    'no-warning-comments': 0,
  },
}

The error message:

Error while loading rule 'vue/no-confusing-v-for-v-if': Cannot read property 'on' of undefined
TypeError: Error while loading rule 'vue/no-confusing-v-for-v-if': Cannot read property 'on' of undefined
    at ensureEmitter (/mnt/d/Projects/tree-select/node_modules/vue-eslint-parser/index.js:2640:23)
    at Object.registerTemplateBodyVisitor (/mnt/d/Projects/tree-select/node_modules/vue-eslint-parser/index.js:2653:29)
    at Object.registerTemplateBodyVisitor (/mnt/d/Projects/tree-select/node_modules/eslint-plugin-vue/lib/utils/index.js:38:28)
    at Object.create (/mnt/d/Projects/tree-select/node_modules/eslint-plugin-vue/lib/rules/no-confusing-v-for-v-if.js:40:9)
    at Object.keys.filter.forEach.key (/mnt/d/Projects/tree-select/node_modules/eslint/lib/linter.js:874:67)
    at Array.forEach (native)
    at Linter.verify (/mnt/d/Projects/tree-select/node_modules/eslint/lib/linter.js:847:93)
    at processText (/mnt/d/Projects/tree-select/node_modules/eslint/lib/cli-engine.js:203:31)
    at processFile (/mnt/d/Projects/tree-select/node_modules/eslint/lib/cli-engine.js:245:18)
    at executeOnFile (/mnt/d/Projects/tree-select/node_modules/eslint/lib/cli-engine.js:585:25)

I have tried downgrading ESLint to 4.3.0 and it solves the problem. So I guess it’s related to the latest release of ESLint.