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

> binary-extensions@3.2.0 is ESM-only. ESM-only since 3.0.0 — last CommonJS version is 2.3.0.

List of binary file extensions

Last verified Sep 9, 2026 against binary-extensions@3.2.0.

binary-extensions dropped its CommonJS build in 3.0.0 (April 2024). The last version with a plain require()-able CommonJS entry is 2.3.0, published Mar 14, 2024; it declares support for Node.js >=8.

On Node.js 20.19+, 22.12+ and newer, require("binary-extensions") works with the latest version: Node.js loads synchronous ES modules through require(). Verified on Node.js 20, 22, 24 and 26. On Node.js 18, which has no require(esm), require("binary-extensions") fails with ERR_REQUIRE_ESM.

## What to do

1. On Node.js 20.19+, 22.12+ and newer, require("binary-extensions") works with the latest version: Node.js loads synchronous ES modules through require(). Verified on Node.js 20, 22, 24 and 26.
2. From a CommonJS file, use a dynamic import inside an async function: const binaryExtensions = await import("binary-extensions"). That works on every Node.js version the package supports (>=18.20).
3. If you need a synchronous require() or run Node.js 18: npm install binary-extensions@2.3.0, the last CommonJS release (published Mar 14, 2024); it declares Node.js >=8.
4. TypeScript: types are bundled; install nothing extra.

## Facts

- Latest: 3.2.0 (Sep 9, 2026)
- Module format: ESM-only
- Last CommonJS version: 2.3.0
- ESM-only since: 3.0.0 (Apr 30, 2024)
- TypeScript types: bundled
- Node engines: >=18.20
- Weekly downloads: 82.0M
- License: MIT

## Runtime test results for binary-extensions@3.2.0

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

| Runtime | require("binary-extensions") | import "binary-extensions" |
|---|---|---|
| Node.js 18 | fails (ERR_REQUIRE_ESM) | 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 binary-extensions

ES modules:

```js
import * as binaryExtensions from "binary-extensions";
```

Namespace import shown because the ESM entry may have no default export; use named imports for what it exports.

CommonJS:

```js
// Node.js 20.19+, 22.12+ and newer (verified):
const binaryExtensions = require("binary-extensions");

// Any Node.js version the package supports (>=18.20), from an async function:
async function main() {
  const binaryExtensions = await import("binary-extensions");
}

// Or pin the last CommonJS release (declares Node.js >=8):
// npm install binary-extensions@2.3.0
```

## Module format by version

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

| Versions | Format | First published |
|---|---|---|
| 3.0.0 – 3.2.0 | ESM-only | Apr 30, 2024 |
| 1.0.0 – 2.3.0 | CommonJS | Jan 24, 2015 |

## Frequently asked

**Is binary-extensions ESM-only?**

binary-extensions@3.2.0 is ESM-only. binary-extensions dropped its CommonJS build in 3.0.0 (April 2024). The last version with a plain require()-able CommonJS entry is 2.3.0, published Mar 14, 2024; it declares support for Node.js >=8.

**Which version of binary-extensions still supports CommonJS / require()?**

2.3.0 is the last version of binary-extensions with a CommonJS build; it declares Node.js >=8. Install it with "npm install binary-extensions@2.3.0". Every version from 3.0.0 on is ESM-only.

**How do I use binary-extensions from a CommonJS file?**

From a CommonJS file, use a dynamic import inside an async function: const binaryExtensions = await import("binary-extensions"). That works on every Node.js version the package supports (>=18.20). On Node.js 20.19+, 22.12+ and newer, require("binary-extensions") works with the latest version: Node.js loads synchronous ES modules through require(). Verified on Node.js 20, 22, 24 and 26. Alternatively pin binary-extensions@2.3.0 (declares Node.js >=8).

**Does binary-extensions work in Bun?**

Yes. import "binary-extensions" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

**Does binary-extensions ship TypeScript types?**

Yes. binary-extensions bundles its own type declarations; no @types package is needed.

## Links

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