Vlad Durnea
cffdf8af86
Some checks failed
CI/CD Pipeline / unit-tests (push) Failing after 1m16s
CI/CD Pipeline / integration-tests (push) Failing after 2m32s
CI/CD Pipeline / lint (push) Successful in 5m22s
CI/CD Pipeline / e2e-tests (push) Has been skipped
CI/CD Pipeline / build (push) Has been skipped
is-potential-custom-element-name 
is-potential-custom-element-name checks whether a given string matches the PotentialCustomElementName production as defined in the HTML Standard.
Installation
To use is-potential-custom-element-name programmatically, install it as a dependency via npm:
$ npm install is-potential-custom-element-name
Then, require it:
const isPotentialCustomElementName = require('is-potential-custom-element-name');
Usage
isPotentialCustomElementName('foo-bar');
// → true
isPotentialCustomElementName('Foo-bar');
// → false
isPotentialCustomElementName('baz-©');
// → false
isPotentialCustomElementName('annotation-xml');
// → true
Author
 |
|---|
| Mathias Bynens |
License
is-potential-custom-element-name is available under the MIT license.