canirequire

canirequire › CommonJS › is-potential-custom-element-name

Is is-potential-custom-element-name ESM-only? Can you require() it?

Check whether a given string matches the `PotentialCustomElementName` production as defined in the HTML Standard.

Last verified Sep 9, 2026 against is-potential-custom-element-name@1.0.1. Markdown · JSON

CommonJS CommonJS — require() works on every Node.js version we test

is-potential-custom-element-name ships CommonJS only. require("is-potential-custom-element-name") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "is-potential-custom-element-name" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.

What to do

  1. require("is-potential-custom-element-name") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun.
  2. From ES modules use the default import: import isPotentialCustomElementName from "is-potential-custom-element-name"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: npm install -D @types/is-potential-custom-element-name
Latest
1.0.1 (Apr 7, 2021)
Module format
CommonJS
Last CommonJS version
1.0.1
TypeScript types
@types/is-potential-custom-element-name
Node engines
not declared
Weekly downloads
41.4M
License
MIT

Does is-potential-custom-element-name@1.0.1 actually load? Runtime test results

Installed and executed on Sep 9, 2026 with require("is-potential-custom-element-name") from a CommonJS file and import "is-potential-custom-element-name" from an ES module.

Runtimerequire("is-potential-custom-element-name")import "is-potential-custom-element-name"
Node.js 18✓ works✓ works
Node.js 20✓ works✓ works
Node.js 22✓ works✓ works
Node.js 24✓ works✓ works
Node.js 26✓ works✓ works
Bun 1.4.0✓ works✓ works

How to import is-potential-custom-element-name

ES modules (import)

import isPotentialCustomElementName from "is-potential-custom-element-name";

Named imports from a CommonJS package only work when Node.js can statically detect them. If a named import fails, use the default import and destructure.

CommonJS (require)

const isPotentialCustomElementName = require("is-potential-custom-element-name");

Module format by version

Derived from the type, main and exports fields of every stable release on npm, corrected where a runtime test of that version contradicted them (2 versions; the newest 2 shown).

VersionsFormatFirst published
1.0.0 – 1.0.1CommonJSJun 21, 2016

Frequently asked

Is is-potential-custom-element-name ESM-only?

is-potential-custom-element-name@1.0.1 is a CommonJS package. is-potential-custom-element-name ships CommonJS only. require("is-potential-custom-element-name") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "is-potential-custom-element-name" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.

Can I import is-potential-custom-element-name with ES module syntax?

Yes. import isPotentialCustomElementName from "is-potential-custom-element-name" works in Node.js and Bun because they support importing CommonJS modules. Named imports work only when Node.js can statically detect the exports.

Does is-potential-custom-element-name work in Bun?

Yes. import "is-potential-custom-element-name" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

Does is-potential-custom-element-name ship TypeScript types?

Not bundled. Install the community types with "npm install -D @types/is-potential-custom-element-name".

Links

Other commonjs packages

Similar popularity