wc/no-invalid-element-name produces error on valid tag names. about eslint-plugin-wc HOT 4 CLOSED

fwiw {loose: true} achieves what was needed by OP. just in case anyone with a similar issue is reading this

from eslint-plugin-wc.

this is basically from the best practices that were published long ago (by google i think)

we follow the same rules they specified back then, which various npm packages also follow for detecting valid element names.

tbh i would probably just disable this rule if you use x- as a prefix. you could also set the options of it {loose: true} which allows those prefixes but disallows invalid names

and maybe in future have a separate rule like an element-name-allowlist or something. to only allow particular patterns

from eslint-plugin-wc.

Could use https://github.com/github/eslint-plugin-custom-elements/blob/main/docs/rules/valid-tag-name.md as an alternative which has a more configurability than this rule.

from eslint-plugin-wc.

closing this as loose mode achieves it, and the new major version will allow clearer customisation of this behaviour

from eslint-plugin-wc.