Tell us about your environment
VSCode 1.27.2
MacBook Pro (Retina, Mid 2012)
_(tested on both versions)_
Please show your full configuration:
// .eslintrc.js
module.exports = {
root: true,
env: {
node: true,
},
extends: ['plugin:vue/recommended'],
parserOptions: {
parser: 'babel-eslint',
},
}
What did you do? Please include the actual source code causing the issue.

<GlobalEvents
:filter="event => event.target.tagName !== 'INPUT' && 'TEXTAREA'"
@keydown.digit1="changeActiveTab(1)"
@keydown.50="test"
/>
What did you expect to happen?
Only report a single eslint error for vue/valid-v-on
What actually happened? Please include the actual, raw output from ESLint.
Reports a 2nd duplicate vue/valid-v-on error, one from the usual eslint source and another from eslint-plugin-vue source which does not react to overrides from my .eslintrc.js. The normal behaviour is for only one error to appear from the eslint source as is obvious from the vue/attributes-order error that only shows up once.
@ashrafhadden Hello!
I think that errors starting with eslint-plugin-vue are reported from theVetur plugin.
I think that you can avoid this issue by making the following settings.
- If you use
Veturplugin in VSCode - set"vetur.validation.template": falseto avoid default Vetur template validation. Check out vetur documentation for more info.
https://github.com/vuejs/eslint-plugin-vue#why-doesnt-it-work-on-vue-file
AHHHH!!! OMG, TY @ota-meshi! 馃檹 xD That totally fixed it :grin:
@michalsnik can you close/resolve this one
Closing as resolved. Thank you!
Most helpful comment
@ashrafhadden Hello!
I think that errors starting with
eslint-plugin-vueare reported from theVeturplugin.I think that you can avoid this issue by making the following settings.
https://github.com/vuejs/eslint-plugin-vue#why-doesnt-it-work-on-vue-file