aacb45156b
- Install Jest for unit testing with React Testing Library - Install Playwright for end-to-end testing - Configure Jest with proper TypeScript support and module mapping - Create test setup files and utilities for both unit and e2e tests Components: * Jest configuration with coverage thresholds * Playwright configuration with browser automation * Unit tests for LoginForm, AuthContext, and useSocketIO hook * E2E tests for authentication, dashboard, and agents workflows * GitHub Actions workflow for automated testing * Mock data and API utilities for consistent testing * Test documentation with best practices Testing features: - Unit tests with 70% coverage threshold - E2E tests with API mocking and user journey testing - CI/CD integration for automated test runs - Cross-browser testing support with Playwright - Authentication system testing end-to-end 🚀 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
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.