canirequire › CommonJS › deep-equal
Is deep-equal ESM-only? Can you require() it?
node's assert.deepEqual algorithm
Last verified Sep 9, 2026 against deep-equal@2.2.3. Markdown · JSON
CommonJS CommonJS — require() works on every Node.js version we test
deep-equal ships CommonJS only. require("deep-equal") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 0.4. import "deep-equal" 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
- require("deep-equal") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 0.4.
- From ES modules use the default import: import deepEqual from "deep-equal"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: npm install -D @types/deep-equal
Does deep-equal@2.2.3 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("deep-equal") from a CommonJS file and import "deep-equal" from an ES module.
| Runtime | require("deep-equal") | import "deep-equal" |
|---|---|---|
| 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 deep-equal
ES modules (import)
import deepEqual from "deep-equal";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 deepEqual = require("deep-equal");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 (22 versions; the newest 22 shown).
| Versions | Format | First published |
|---|---|---|
| 0.0.0 – 2.2.3 | CommonJS | Feb 11, 2012 |
Frequently asked
Is deep-equal ESM-only?
deep-equal@2.2.3 is a CommonJS package. deep-equal ships CommonJS only. require("deep-equal") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 0.4. import "deep-equal" 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 deep-equal with ES module syntax?
Yes. import deepEqual from "deep-equal" 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 deep-equal work in Bun?
Yes. import "deep-equal" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does deep-equal ship TypeScript types?
Not bundled. Install the community types with "npm install -D @types/deep-equal".
Links
Other commonjs packages
- debug 4.4.3CommonJS
- semver 7.8.5CommonJS
- ms 2.1.3CommonJS
- picomatch 4.0.7CommonJS
- ajv 8.20.0CommonJS
- source-map 0.8.0CommonJS
- react-is 19.2.8CommonJS
- readable-stream 4.7.0CommonJS
Similar popularity
- @smithy/util-base64 4.6.2CommonJS
- reflect-metadata 0.2.2CommonJS
- @smithy/middleware-serde 4.5.2CommonJS
- @smithy/url-parser 4.5.2CommonJS
- @smithy/config-resolver 4.7.2CommonJS
- @smithy/util-hex-encoding 4.5.2CommonJS
- got 16.0.0ESM-only
- sass 1.104.0Dual