athea

Repositories Projects Packages

is-potential-custom-element-name (1.0.1)

Published 2026-02-24 13:58:35 +00:00 by atheaadmin

Installation

Setup this registry in your project .npmrc file:

registry=

To install the package using npm, run the following command:

npm install is-potential-custom-element-name@1.0.1

or add it to the package.json file:

"is-potential-custom-element-name": "1.0.1"

For more information on the npm registry, see the documentation.

About this package

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.

Dependencies

Development Dependencies

ID	Version
mocha	^2.2.1
regenerate	^1.4.2

Keywords

html custom element custom element name web components

Details

npm

2026-02-24 13:58:35 +00:00

1

Mathias Bynens

Project Site

MIT

latest

1.9 KiB

Assets (1)

is-potential-custom-element-name-1.0.1.tgz 1.9 KiB

Versions (1) View all

1.0.1 2026-02-24