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

> is-binary-path@3.0.0 is ESM-only. ESM-only since 3.0.0 — last CommonJS version is 2.1.0.

Check if a file path is a binary file

Last verified Sep 9, 2026 against is-binary-path@3.0.0.

is-binary-path dropped its CommonJS build in 3.0.0 (April 2024). The last version with a plain require()-able CommonJS entry is 2.1.0, published Apr 19, 2019; it declares support for Node.js >=8.

On Node.js 20.19+, 22.12+ and newer, require("is-binary-path") 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("is-binary-path") fails with ERR_REQUIRE_ESM.

## What to do

1. On Node.js 20.19+, 22.12+ and newer, require("is-binary-path") 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 isBinaryPath = await import("is-binary-path"). 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 is-binary-path@2.1.0, the last CommonJS release (published Apr 19, 2019); it declares Node.js >=8.
4. TypeScript: types are bundled; install nothing extra.

## Facts

- Latest: 3.0.0 (Apr 30, 2024)
- Module format: ESM-only
- Last CommonJS version: 2.1.0
- ESM-only since: 3.0.0 (Apr 30, 2024)
- TypeScript types: bundled
- Node engines: >=18.20
- Weekly downloads: 47.1M
- License: MIT

## Runtime test results for is-binary-path@3.0.0

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

| Runtime | require("is-binary-path") | import "is-binary-path" |
|---|---|---|
| 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 is-binary-path

ES modules:

```js
import * as isBinaryPath from "is-binary-path";
```

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 isBinaryPath = require("is-binary-path");

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

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

## Module format by version

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

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

## Frequently asked

**Is is-binary-path ESM-only?**

is-binary-path@3.0.0 is ESM-only. is-binary-path dropped its CommonJS build in 3.0.0 (April 2024). The last version with a plain require()-able CommonJS entry is 2.1.0, published Apr 19, 2019; it declares support for Node.js >=8.

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

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

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

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

**Does is-binary-path work in Bun?**

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

**Does is-binary-path ship TypeScript types?**

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

## Links

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