JSPM

is-potential-custom-element-name

1.0.1
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 26958501
  • Score
    100M100P100Q249072F
  • License MIT

Check whether a given string matches the `PotentialCustomElementName` production as defined in the HTML Standard.

Package Exports

  • is-potential-custom-element-name

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (is-potential-custom-element-name) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

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.