- web/: Vue 3 + Vite + UnoCSS + Pinia, dark tactical theme (amber/#0d1117) - AppNav, ListingCard, SearchView with filters/sort, composables (useSnipeMode, useKonamiCode, useMotion), Pinia search store - Steal shimmer, auction countdown, Snipe Mode easter egg all native in Vue - docker/web/: nginx + multi-stage Dockerfile (node build → nginx serve) - compose.yml: api (8510) + web (8509) services - Dockerfile CMD updated to uvicorn for upcoming FastAPI layer - Clean build: 0 TS errors, 380 modules |
||
|---|---|---|
| .. | ||
| index.js | ||
| LICENSE-MIT.txt | ||
| package.json | ||
| 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.