Archived

This repository has been archived on 2023-05-15. You can view files and clone it. You cannot open issues or pull requests or push a commit.

Files

History

Sean Edmunds 3e953ad8d2 v1.1 update - stable

this version will run with npm start, but when attempting to run the built version behind nginx, it appears to have issues

2021-12-15 01:48:50 +00:00

index.js

First commit

2021-12-13 17:00:40 -06:00

LICENSE-MIT.txt

First commit

2021-12-13 17:00:40 -06:00

package.json

v1.1 update - stable

2021-12-15 01:48:50 +00:00

README.md

First commit

2021-12-13 17:00:40 -06:00

README.md

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.