validate-element-name
Advanced tools
Validate the name of a custom element
Custom element names should start with a-z and contain a-z and at least one - with optionally 0-9.
You should not use the x- or polymer- prefix.
$ npm install --save validate-element-name
var validate = require('validate-element-name');
try {
validate('unicorn');
} catch (err) {
console.log(err.message);
//=> 'Custom element names must contain a hyphen. Example: unicorn-cake'
}
Throws an error if the custom element name is invalid.
You can also use it as a CLI app by installing it globally:
$ npm install --global validate-element-name
$ validate-element-name --help
Usage
$ validate-element-name <element-name>
Example
$ validate-element-name s-slider
Valid element name 👍
FAQs
Validate the name of a custom element
We found that validate-element-name demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Snyk's use of malicious npm packages for research raises ethical concerns, highlighting risks in public deployment, data exfiltration, and unauthorized testing.
Research
Security News
Socket researchers found several malicious npm packages typosquatting Chalk and Chokidar, targeting Node.js developers with kill switches and data theft.
Security News
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.