canirequire

canirequire › CommonJS › enzyme

Is enzyme ESM-only? Can you require() it?

JavaScript Testing utilities for React

Last verified Sep 9, 2026 against enzyme@3.11.0. Markdown · JSON

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

enzyme declares a CommonJS entry only, but require("enzyme") failed on every Node.js version in our probe: ERR_PACKAGE_PATH_NOT_EXPORTED. import "enzyme" 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("enzyme") failed in our probe on every Node.js version (ERR_PACKAGE_PATH_NOT_EXPORTED); check the package README for peer dependencies or setup before relying on it.
  2. From ES modules use the default import: import enzyme from "enzyme"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: npm install -D @types/enzyme
Latest
3.11.0 (Dec 20, 2019)
Module format
CommonJS
Last CommonJS version
3.11.0
TypeScript types
@types/enzyme
Node engines
not declared
Weekly downloads
1.2M
License
MIT

Does enzyme@3.11.0 actually load? Runtime test results

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

Runtimerequire("enzyme")import "enzyme"
Node.js 18✗ failsReferenceError✗ failsReferenceError
Node.js 20✗ failsERR_PACKAGE_PATH_NOT_EXPORTED✗ failsERR_PACKAGE_PATH_NOT_EXPORTED
Node.js 22✗ failsERR_PACKAGE_PATH_NOT_EXPORTED✗ failsERR_PACKAGE_PATH_NOT_EXPORTED
Node.js 24✗ failsERR_PACKAGE_PATH_NOT_EXPORTED✗ failsERR_PACKAGE_PATH_NOT_EXPORTED
Node.js 26✗ failsERR_PACKAGE_PATH_NOT_EXPORTED✗ failsERR_PACKAGE_PATH_NOT_EXPORTED
Bun 1.4.0✗ failsError✗ failsError

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 enzyme

ES modules (import)

import enzyme from "enzyme";

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("enzyme") failed in our probe on every Node.js version we test (ERR_PACKAGE_PATH_NOT_EXPORTED); see the runtime table.
const enzyme = require("enzyme");

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

VersionsFormatFirst published
1.0.0 – 3.11.0CommonJSDec 6, 2015

Frequently asked

Is enzyme ESM-only?

enzyme@3.11.0 declares a CommonJS entry, but require() fails at runtime. enzyme declares a CommonJS entry only, but require("enzyme") failed on every Node.js version in our probe: ERR_PACKAGE_PATH_NOT_EXPORTED. import "enzyme" 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 enzyme?

Not in practice. enzyme declares a CommonJS entry, but require("enzyme") failed on every Node.js version in our probe: ERR_PACKAGE_PATH_NOT_EXPORTED. Check the package README for peer dependencies or setup before relying on it.

Can I import enzyme with ES module syntax?

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

Importing enzyme failed in Bun 1.4.0 on Sep 9, 2026: error: Cannot find module 'cheerio/lib/utils' from '/Users/boat/Projects/top-seo/data/probe-work/enzyme/node_modules/enzyme/build/Utils.js'

Does enzyme ship TypeScript types?

Not bundled. Install the community types with "npm install -D @types/enzyme".

Links

Other commonjs packages

Similar popularity