canirequire › CommonJS › extend
Is extend ESM-only? Can you require() it?
Port of jQuery.extend for node.js and the browser
Last verified Sep 9, 2026 against extend@3.0.2. Markdown · JSON
CommonJS CommonJS — require() works on every Node.js version we test
extend ships CommonJS only. require("extend") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "extend" 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("extend") 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 extend from "extend"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: npm install -D @types/extend
Does extend@3.0.2 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("extend") from a CommonJS file and import "extend" from an ES module.
| Runtime | require("extend") | import "extend" |
|---|---|---|
| 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 extend
ES modules (import)
import extend from "extend";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 extend = require("extend");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 (13 versions; the newest 13 shown).
| Versions | Format | First published |
|---|---|---|
| 1.0.0 – 3.0.2 | CommonJS | May 14, 2011 |
Frequently asked
Is extend ESM-only?
extend@3.0.2 is a CommonJS package. extend ships CommonJS only. require("extend") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "extend" 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 extend with ES module syntax?
Yes. import extend from "extend" 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 extend work in Bun?
Yes. import "extend" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does extend ship TypeScript types?
Not bundled. Install the community types with "npm install -D @types/extend".
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
- d3-color 3.1.0ESM-only
- which-builtin-type 1.2.1CommonJS
- @babel/plugin-syntax-typescript 8.0.3ESM-only
- is-async-function 2.1.1CommonJS
- @floating-ui/utils 0.2.12Dual
- @csstools/css-parser-algorithms 4.0.0ESM-only
- nopt 10.0.1CommonJS
- own-keys 1.0.2CommonJS