Files

T

gnezim 0a5ab058a6 Initial commit: Aeroflot Flights Web - Angular 12 baseline

- Angular 12 application with PrimeNG components
- 5 existing Cypress e2e test suites
- SCSS styling with BEM naming convention
- i18n support (10 languages)
- Leaflet map integration
- Complete component hierarchy and routing structure

This baseline will be used for Angular → React migration.

2026-04-05 18:47:57 +03:00

index.js

Initial commit: Aeroflot Flights Web - Angular 12 baseline

2026-04-05 18:47:57 +03:00

LICENSE-MIT.txt

Initial commit: Aeroflot Flights Web - Angular 12 baseline

2026-04-05 18:47:57 +03:00

package.json

Initial commit: Aeroflot Flights Web - Angular 12 baseline

2026-04-05 18:47:57 +03:00

README.md

Initial commit: Aeroflot Flights Web - Angular 12 baseline

2026-04-05 18:47:57 +03:00

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.