canirequire › ESM-only › binary-extensions
Is binary-extensions ESM-only? Can you require() it?
List of binary file extensions
Last verified Sep 9, 2026 against binary-extensions@3.2.0. Markdown · JSON
ESM-only ESM-only since 3.0.0 — last CommonJS version is 2.3.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
- 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.
- 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).
- 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.
- TypeScript: types are bundled; install nothing extra.
Does binary-extensions@3.2.0 actually load? Runtime test results
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 | ✗ failsERR_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 (import)
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 (require)
// 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.0Module 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 (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
Other esm-only packages
- ansi-styles 7.0.0last CJS
5.2.0 - strip-ansi 7.2.0last CJS
6.0.1 - commander 15.0.0last CJS
14.0.3 - supports-color 11.0.0last CJS
8.1.1 - chalk 6.0.0last CJS
4.1.2 - string-width 8.2.2last CJS
4.2.3 - ansi-regex 6.3.0last CJS
5.0.1 - escape-string-regexp 5.0.0last CJS
4.0.0
Similar popularity
- mute-stream 4.0.0CommonJS
- @radix-ui/react-use-controllable-state 1.2.6Dual
- ip-address 10.7.0CommonJS
- @aws-sdk/token-providers 3.1128.0CommonJS
- @sinclair/typebox 0.34.52Dual
- is-generator-function 1.1.2CommonJS
- @eslint/config-array 0.23.5Dual
- @aws-sdk/core 3.977.9Dual