canirequire › CommonJS › lodash.clonedeep
Is lodash.clonedeep ESM-only? Can you require() it?
The lodash method `_.cloneDeep` exported as a module.
Last verified Sep 9, 2026 against lodash.clonedeep@4.5.0. Markdown · JSON
CommonJS CommonJS — require() works on every Node.js version we test
lodash.clonedeep ships CommonJS only. require("lodash.clonedeep") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "lodash.clonedeep" 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("lodash.clonedeep") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun.
- From ES modules use the default import: import lodashClonedeep from "lodash.clonedeep"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: npm install -D @types/lodash.clonedeep
Does lodash.clonedeep@4.5.0 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("lodash.clonedeep") from a CommonJS file and import "lodash.clonedeep" from an ES module.
| Runtime | require("lodash.clonedeep") | import "lodash.clonedeep" |
|---|---|---|
| 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 lodash.clonedeep
ES modules (import)
import lodashClonedeep from "lodash.clonedeep";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 lodashClonedeep = require("lodash.clonedeep");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 (24 versions; the newest 24 shown).
| Versions | Format | First published |
|---|---|---|
| 2.0.0 – 4.5.0 | CommonJS | Sep 23, 2013 |
Frequently asked
Is lodash.clonedeep ESM-only?
lodash.clonedeep@4.5.0 is a CommonJS package. lodash.clonedeep ships CommonJS only. require("lodash.clonedeep") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "lodash.clonedeep" 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 lodash.clonedeep with ES module syntax?
Yes. import lodashClonedeep from "lodash.clonedeep" 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 lodash.clonedeep work in Bun?
Yes. import "lodash.clonedeep" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does lodash.clonedeep ship TypeScript types?
Not bundled. Install the community types with "npm install -D @types/lodash.clonedeep".
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
- change-case 5.4.4ESM-only
- boxen 8.0.1ESM-only
- underscore 1.13.8Dual
- i18next 26.4.2Dual
- storybook 10.6.0ESM-only
- @rollup/plugin-commonjs 29.0.3Dual
- clean-css 5.3.3CommonJS
- fork-ts-checker-webpack-plugin 9.1.0CommonJS