# Is xtend ESM-only? Can you require() it?

> xtend@4.0.2 is a CommonJS package. CommonJS — require() works on every Node.js version we test.

extend like a boss

Last verified Sep 9, 2026 against xtend@4.0.2.

xtend ships CommonJS only. require("xtend") 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 "xtend" 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

1. require("xtend") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=0.4.
2. From ES modules use the default import: import xtend from "xtend"; then destructure. Named imports only work when Node.js can statically detect the exports.
3. TypeScript: npm install -D @types/xtend

## Facts

- Latest: 4.0.2 (Jul 8, 2019)
- Module format: CommonJS
- Last CommonJS version: 4.0.2
- TypeScript types: @types/xtend
- Node engines: >=0.4
- Weekly downloads: 61.4M
- License: MIT

## Runtime test results for xtend@4.0.2

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

| Runtime | require("xtend") | import "xtend" |
|---|---|---|
| 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 xtend

ES modules:

```js
import xtend from "xtend";
```

CommonJS:

```js
const xtend = require("xtend");
```

## Module format by version

Derived from the type, main and exports fields of every stable release on npm (17 versions; the newest 17 shown).

| Versions | Format | First published |
|---|---|---|
| 1.0.0 – 4.0.2 | CommonJS | May 23, 2012 |

## Frequently asked

**Is xtend ESM-only?**

xtend@4.0.2 is a CommonJS package. xtend ships CommonJS only. require("xtend") 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 "xtend" 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 xtend with ES module syntax?**

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

Yes. import "xtend" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

**Does xtend ship TypeScript types?**

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

## Links

- [xtend on npm](https://www.npmjs.com/package/xtend)
- [Source repository](https://github.com/Raynos/xtend)
- [HTML version](https://canirequire.com/package/xtend/)
- [JSON version](https://canirequire.com/package/xtend.json)

---

For scripts and AI agents: any package is at https://canirequire.com/package/<name>/index.md (Markdown) or https://canirequire.com/package/<name>.json (JSON); the site index is https://canirequire.com/llms.txt. Fetch the URL directly; no search needed.