Files

root f6fac6c4bc Fix bin/publish: copy docs.dist from project root

Fix bin/publish: use correct .env path for rspade_system
Fix bin/publish script: prevent grep exit code 1 from terminating script

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

2025-10-21 02:08:33 +00:00

1.3 KiB

Executable File

Raw Blame History

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.

1.3 KiB Executable File Raw Blame History