canirequire

canirequire › CommonJS › element-ui

Is element-ui ESM-only? Can you require() it?

A Component Library for Vue.js.

Last verified Sep 9, 2026 against element-ui@2.15.14. Markdown · JSON

CommonJS CommonJS on paper — require() failed in our runtime test

element-ui declares a CommonJS entry only, but require("element-ui") failed on every Node.js version in our probe: ReferenceError: document is not defined. import "element-ui" resolves to the same file, so it fails the same way. That usually means a missing peer dependency, a browser-only global, or a package that is not meant to be loaded directly; see the runtime table below.

What to do

  1. require("element-ui") failed in our probe on every Node.js version (ReferenceError: document is not defined); check the package README for peer dependencies or setup before relying on it.
  2. From ES modules use the default import: import elementUi from "element-ui"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: types are bundled; install nothing extra.
Latest
2.15.14 (Aug 24, 2023)
Module format
CommonJS
Last CommonJS version
2.15.14
TypeScript types
Bundled
Node engines
not declared
Weekly downloads
105K
License
MIT

Does element-ui@2.15.14 actually load? Runtime test results

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

Runtimerequire("element-ui")import "element-ui"
Node.js 18✗ failsReferenceError✗ failsReferenceError
Node.js 20✗ failsReferenceError✗ failsReferenceError
Node.js 22✗ failsReferenceError✗ failsReferenceError
Node.js 24✗ failsReferenceError✗ failsReferenceError
Node.js 26✗ failsReferenceError✗ failsReferenceError
Bun 1.4.0✗ failsReferenceError✗ failsReferenceError

A failing require() on a CommonJS package usually means the package needs a browser/DOM global, a peer dependency, or a native binary that is not available in a bare Node.js process.

How to import element-ui

ES modules (import)

import elementUi from "element-ui";

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)

// require("element-ui") failed in our probe on every Node.js version we test (ReferenceError: document is not defined); see the runtime table.
const elementUi = require("element-ui");

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 (147 versions; the newest 60 shown).

VersionsFormatFirst published
2.3.5 – 2.15.14CommonJSApr 20, 2018

Frequently asked

Is element-ui ESM-only?

element-ui@2.15.14 declares a CommonJS entry, but require() fails at runtime. element-ui declares a CommonJS entry only, but require("element-ui") failed on every Node.js version in our probe: ReferenceError: document is not defined. import "element-ui" resolves to the same file, so it fails the same way. That usually means a missing peer dependency, a browser-only global, or a package that is not meant to be loaded directly; see the runtime table below.

Can I require element-ui?

Not in practice. element-ui declares a CommonJS entry, but require("element-ui") failed on every Node.js version in our probe: ReferenceError: document is not defined. Check the package README for peer dependencies or setup before relying on it.

Can I import element-ui with ES module syntax?

Yes. import elementUi from "element-ui" 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 element-ui work in Bun?

Importing element-ui failed in Bun 1.4.0 on Sep 9, 2026: ReferenceError: document is not defined

Does element-ui ship TypeScript types?

Yes. element-ui bundles its own type declarations; no @types package is needed.

Links

Other commonjs packages

Similar popularity