is-potential-custom-element-name
npmv1.0.1Check whether a given string matches the `PotentialCustomElementName` production as defined in the HTML Standard.
Not recommended for new projects
No — is-potential-custom-element-name should not be adopted for new projects. Last published 1981 days ago.
- AAdoption: grade A, Excellent.
41.4M downloads per week and 2 known dependents.
- FMaintenance: grade F, Failing.
Last published 1981 days ago.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 3.8 KB installed.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- ALicense: grade A, Excellent.
MIT — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding is-potential-custom-element-name to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Node.js
- No constraint declared
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the is-potential-custom-element-name README.
const isPotentialCustomElementName = require('is-potential-custom-element-name');is-potential-custom-element-name vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| is-potential-custom-element-namethis page | 41.4M | 2 | MIT | 5 years ago |
| dom-serializer | 94.3M | 2 | MIT | 1 day ago |
| html-escaper | 79.8M | 1 | MIT | 1 day ago |
| cheerio | 24.1M | 5 | MIT | 1 day ago |
| anser | 10.4M | 3 | MIT | 1 day ago |
| @vitest/ui | 8.9M | 9 | MIT | 1 day ago |
Dependencies
Declared by is-potential-custom-element-name v1.0.1. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (2)
Used by
Popular packages that depend on is-potential-custom-element-name.
Relationship graph
Dependencies (left) and dependents (right) of is-potential-custom-element-name.
Frequently installed together
An AST-based pattern checker for JavaScript.
A tool set for CSS: fast detailed parser (CSS → AST), walker (AST traversal), generator (AST → CSS) and lexer (validation and matching) based on specs and browser implementations
🔎 A simple, tiny and lightweight benchmarking library!
the complete solution for node.js command-line programs
Prettier is an opinionated code formatter
A JavaScript implementation of the Unicode Bidirectional Algorithm
A JavaScript implementation of many web standards
BDD/TDD assertion library for node.js and the browser. Test framework agnostic.
TypeScript definitions for node
An implementation of the WHATWG URL Standard's URL API and parsing machinery
An HTTP/1.1 client, written from scratch for Node.js
Implements the WebIDL algorithms for converting to and from JavaScript values
Release history
No releases in the last two years.
| Version | Published | Size | License |
|---|---|---|---|
| 1.0.1latest | 5 years ago | 3.8 KB | MIT |
| 1.0.0 | 10 years ago | — | MIT |
Overview
is-potential-custom-element-name is an npm package that check whether a given string matches the `PotentialCustomElementName` production as defined in the HTML Standard. It is extremely widely used, with about 41.4M downloads per week and 2 known dependents in the graph. The latest version is 1.0.1, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need check whether a given string matches the `PotentialCustomElementName` production as defined in the HTML Standard and value a battle-tested, widely-adopted solution.
When not to use it
Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.
Pros
- Large, well-established user base (41.4M weekly downloads).
- Clear open-source license (MIT).
- Lean dependency tree (2 direct dependencies).
Cons
- No bundled TypeScript types (may require a separate @types package).
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use is-potential-custom-element-name?
No — is-potential-custom-element-name should not be adopted for new projects. Last published 1981 days ago.
How do I install is-potential-custom-element-name?
Run `npm install is-potential-custom-element-name` to add is-potential-custom-element-name to your npm project.
What license is is-potential-custom-element-name released under?
is-potential-custom-element-name is distributed under the MIT license.
How popular is is-potential-custom-element-name?
is-potential-custom-element-name has approximately 41,404,427 downloads per week and 2 known dependent packages.
Is is-potential-custom-element-name still maintained?
The most recent release of is-potential-custom-element-name (v1.0.1) was published 5 years ago.
Does is-potential-custom-element-name run install scripts?
No. is-potential-custom-element-name does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.