securityos/node_modules/is-potential-custom-element...
Berkeley 927854894b First commit 2024-09-06 12:32:35 -03:00
..
LICENSE-MIT.txt First commit 2024-09-06 12:32:35 -03:00
README.md First commit 2024-09-06 12:32:35 -03:00
index.js First commit 2024-09-06 12:32:35 -03:00
package.json First commit 2024-09-06 12:32:35 -03:00

README.md

is-potential-custom-element-name Build status

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

twitter/mathias
Mathias Bynens

License

is-potential-custom-element-name is available under the MIT license.