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

> human-signals@8.0.1 is ESM-only. ESM-only since 3.0.0 — last CommonJS version is 2.1.0.

Human-friendly process signals

Last verified Sep 9, 2026 against human-signals@8.0.1.

human-signals dropped its CommonJS build in 3.0.0 (June 2021). The last version with a plain require()-able CommonJS entry is 2.1.0, published Mar 14, 2020; it declares support for Node.js >=10.17.0.

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

## What to do

1. On Node.js 20.19+, 22.12+ and newer, require("human-signals") 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 humanSignals = await import("human-signals"). That works on every Node.js version the package supports (>=18.18.0).
3. If you need a synchronous require() or run Node.js 18: npm install human-signals@2.1.0, the last CommonJS release (published Mar 14, 2020); it declares Node.js >=10.17.0.
4. TypeScript: types are bundled; install nothing extra.

## Facts

- Latest: 8.0.1 (Mar 29, 2025)
- Module format: ESM-only
- Last CommonJS version: 2.1.0
- ESM-only since: 3.0.0 (Jun 22, 2021)
- TypeScript types: bundled
- Node engines: >=18.18.0
- Weekly downloads: 75.2M
- License: Apache-2.0

## Runtime test results for human-signals@8.0.1

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

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

ES modules:

```js
import * as humanSignals from "human-signals";
```

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 humanSignals = require("human-signals");

// Any Node.js version the package supports (>=18.18.0), from an async function:
async function main() {
  const humanSignals = await import("human-signals");
}

// Or pin the last CommonJS release (declares Node.js >=10.17.0):
// npm install human-signals@2.1.0
```

## Module format by version

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

| Versions | Format | First published |
|---|---|---|
| 3.0.0 – 8.0.1 | ESM-only | Jun 22, 2021 |
| 1.1.0 – 2.1.0 | CommonJS | Oct 12, 2019 |

## Frequently asked

**Is human-signals ESM-only?**

human-signals@8.0.1 is ESM-only. human-signals dropped its CommonJS build in 3.0.0 (June 2021). The last version with a plain require()-able CommonJS entry is 2.1.0, published Mar 14, 2020; it declares support for Node.js >=10.17.0.

**Which version of human-signals still supports CommonJS / require()?**

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

**How do I use human-signals from a CommonJS file?**

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

**Does human-signals work in Bun?**

Yes. import "human-signals" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

**Does human-signals ship TypeScript types?**

Yes. human-signals bundles its own type declarations; no @types package is needed.

## Links

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