Some checks failed
Test Suite / code-quality (push) Has been cancelled
Test Suite / unit-tests (3.11) (push) Has been cancelled
Test Suite / unit-tests (3.12) (push) Has been cancelled
Test Suite / security-scan (push) Has been cancelled
Test Suite / integration-tests (push) Has been cancelled
Test Suite / e2e-tests (push) Has been cancelled
Test Suite / performance-tests (push) Has been cancelled
Test Suite / test-summary (push) Has been cancelled
1.3 KiB
1.3 KiB
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.