I am about to release a new major version ofeslint-plugin-html and it will not export processors anymore, sothis won't work anymore. Of course if you don't change youreslint-plugin-html dependency version everything will be fine, but I don't plan to maintain the v1, and the v2 has long awaited features like theeslint --fix support, which might interest you.

My plugin isn't exposing processors anymore because the current eslint system is too limited (e.i.: doesn't support --fix), and I wanted users to be able to configure the html file extensions they want (most of my plugin PR was about adding new file extensions). Instead, it patches some ESLint functions as soon as it is required. It seems scarry but it already did it from the beginning and it worked correctly since then.

So one solution would be to simplyrequire("eslint-plugin-html"); in your plugin and that's it..vue files are already considered as HTML by default, but if you want to override the default toonly lint.vue files, you can add the following setting ineslint-config-vue:

"settings": {"html/html-extensions": [".vue"],"html/xml-extensions": []    }

Seedocumentation andchangelog. I released the v2 as a beta tag, so you can try it withnpm i eslint-plugin-html@beta.

Let me know if you have any concern about those changes.