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

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

Copy file globs, watching for changes.

Last verified Sep 9, 2026 against cpx@1.5.0.

cpx ships CommonJS only. require("cpx") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "cpx" 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("cpx") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun.
2. From ES modules use the default import: import cpx from "cpx"; then destructure. Named imports only work when Node.js can statically detect the exports.
3. TypeScript: npm install -D @types/cpx

## Facts

- Latest: 1.5.0 (Sep 4, 2016)
- Module format: CommonJS
- Last CommonJS version: 1.5.0
- TypeScript types: @types/cpx
- Node engines: not declared
- Weekly downloads: 237K
- License: MIT

## Runtime test results for cpx@1.5.0

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

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

ES modules:

```js
import cpx from "cpx";
```

CommonJS:

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

## Module format by version

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

| Versions | Format | First published |
|---|---|---|
| 1.0.0 – 1.5.0 | CommonJS | Mar 8, 2015 |

## Frequently asked

**Is cpx ESM-only?**

cpx@1.5.0 is a CommonJS package. cpx ships CommonJS only. require("cpx") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "cpx" 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 cpx with ES module syntax?**

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

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

**Does cpx ship TypeScript types?**

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

## Links

- [cpx on npm](https://www.npmjs.com/package/cpx)
- [Source repository](https://github.com/mysticatea/cpx)
- [HTML version](https://canirequire.com/package/cpx/)
- [JSON version](https://canirequire.com/package/cpx.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.