canirequire

canirequire › ESM-only › execa

Is execa ESM-only? Can you require() it?

Process execution for humans

Last verified Sep 9, 2026 against execa@10.0.1. Markdown · JSON

ESM-only ESM-only since 6.0.0 — last CommonJS version is 5.1.1

execa dropped its CommonJS build in 6.0.0 (November 2021). The last version with a plain require()-able CommonJS entry is 5.1.1, published Jun 4, 2021; it declares support for Node.js >=10.

On Node.js 22.12+ and newer (execa@10.0.1 declares Node.js >=22), require("execa") works with the latest version: Node.js loads synchronous ES modules through require(). Verified on Node.js 22, 24 and 26. Node.js 18 has no require(esm), and execa@10.0.1 declares Node.js >=22, so 18 is outside its supported range anyway.

execa@10.0.1 declares engines ">=22", so Node.js 18, 20 are outside its supported range regardless of module format.

What to do

  1. On Node.js 22.12+ and newer (execa@10.0.1 declares Node.js >=22), require("execa") works with the latest version: Node.js loads synchronous ES modules through require(). Verified on Node.js 22, 24 and 26.
  2. From a CommonJS file, use a dynamic import inside an async function: const execa = await import("execa"). That works on every Node.js version the package supports (>=22).
  3. If you need a synchronous require() or run Node.js 18: npm install execa@5.1.1, the last CommonJS release (published Jun 4, 2021); it declares Node.js >=10.
  4. execa@10.0.1 declares engines ">=22", so Node.js 18, 20 are unsupported regardless: upgrade Node.js or pin an older release.
  5. TypeScript: types are bundled; install nothing extra.
Latest
10.0.1 (Jul 31, 2026)
Module format
ESM-only
Last CommonJS version
5.1.1
ESM-only since
6.0.0 (Nov 17, 2021)
TypeScript types
Bundled
Node engines
>=22
Weekly downloads
150.6M
License
MIT

Does execa@10.0.1 actually load? Runtime test results

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

Runtimerequire("execa")import "execa"
Node.js 18✗ failsERR_REQUIRE_ESM✗ failsSyntaxError
Node.js 20✗ failsTypeError✗ failsTypeError
Node.js 22✓ works✓ works
Node.js 24✓ works✓ works
Node.js 26✓ works✓ works
Bun 1.4.0✓ works✓ works

How to import execa

ES modules (import)

import * as execa from "execa";

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

CommonJS (require)

// Node.js 22.12+ and newer (verified):
const execa = require("execa");

// Any Node.js version the package supports (>=22), from an async function:
async function main() {
  const execa = await import("execa");
}

// Or pin the last CommonJS release (declares Node.js >=10):
// npm install execa@5.1.1

Module 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 (65 versions; the newest 60 shown).

VersionsFormatFirst published
6.0.0 – 10.0.1ESM-onlyNov 17, 2021
0.3.0 – 5.1.1CommonJSApr 22, 2016

Frequently asked

Is execa ESM-only?

execa@10.0.1 is ESM-only. execa dropped its CommonJS build in 6.0.0 (November 2021). The last version with a plain require()-able CommonJS entry is 5.1.1, published Jun 4, 2021; it declares support for Node.js >=10.

Which version of execa still supports CommonJS / require()?

5.1.1 is the last version of execa with a CommonJS build; it declares Node.js >=10. Install it with "npm install execa@5.1.1". Every version from 6.0.0 on is ESM-only.

How do I use execa from a CommonJS file?

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

Does execa work in Bun?

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

Does execa ship TypeScript types?

Yes. execa bundles its own type declarations; no @types package is needed.

Links

Other esm-only packages

Similar popularity