is-potential-custom-element-name
Check whether a given string matches the `PotentialCustomElementName` production as defined in the HTML Standard.
Last updated 4 years ago by mathias .
MIT · Repository · Bugs · Original npm · Tarball · package.json
$ gnpm install is-potential-custom-element-name 
SYNC missed versions from official npm registry.

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.

Current Tags

  • 1.0.1                                ...           latest (4 years ago)

2 Versions

  • 1.0.1                                ...           4 years ago
  • 1.0.0                                ...           8 years ago
Maintainers (1)
Downloads
Today 0
This Week 0
This Month 0
Last Day 0
Last Week 0
Last Month 0
Dependencies (0)
None
Dev Dependencies (2)
Dependents (1)

Copyright 2013 - present © cnpmjs.org | Home |