I discussed this with @koddsson. We think this needs to change a little. We think this would be best suited as an option. Rather than broadening the RegExp, rules which use these RegExps should be able to pass in the desired superclass, so for e.g. if you're using a library and need to extend from VendorHTMLElement, you can explicitly put VendorHTMLELement as the superclass for the applicable rules.

I discussed this with @koddsson. We think this needs to change a little. We think this would be best suited as an option. Rather than broadening the RegExp, rules which use these RegExps should be able to pass in the desired superclass, so for e.g. if you're using a library and need to extend from VendorHTMLElement, you can explicitly put VendorHTMLELement as the superclass for the applicable rules.

Thanks for the discussion! Does ESLint have a global way to assign options for multiple rules, say similar to the allowlist in #38 but on a plugin-wide level?

Otherwise, I worry that it may be tedious to specify a superclass for each rule.

This is also the last change I had made in our fork of eslint-plugin-custom-elements, but I'm not super opinionated on it. Do you think HTMLVendorElement would make more sense? If so, I'm happy to make those changes so we can move upstream.

Does ESLint have a global way to assign options for multiple rules

That's what settings is for, but keep note that this is legacy eslint config format, it might be different for the flat config format.

This project has now been merged with eslint-plugin-wc. Please head there for updates and maintenance.