# Is @humanfs/core ESM-only? Can you require() it?

> @humanfs/core@0.19.2 is ESM-only. ESM-only — it has never shipped a CommonJS build.

The core of the humanfs library.

Last verified Sep 9, 2026 against @humanfs/core@0.19.2.

@humanfs/core has been ESM-only since its first stable release; there is no CommonJS version to pin.

require("@humanfs/core") failed in our probe on Node.js 20+ as well; see the runtime table for the error before relying on it. On Node.js 18, which has no require(esm), require("@humanfs/core") fails with ERR_REQUIRE_ESM.

## What to do

1. require("@humanfs/core") failed in our probe on Node.js 20+ as well; see the runtime table for the error before relying on it.
2. From a CommonJS file, use a dynamic import inside an async function: const core = await import("@humanfs/core"). That works on every Node.js version the package supports (>=18.18.0).
3. There is no CommonJS release of @humanfs/core to pin; without require(esm) the only option is a dynamic import().
4. TypeScript: types are bundled; install nothing extra.

## Facts

- Latest: 0.19.2 (Apr 17, 2026)
- Module format: ESM-only
- Last CommonJS version: none
- ESM-only since: 0.6.0 (Jan 30, 2024)
- TypeScript types: bundled
- Node engines: >=18.18.0
- Weekly downloads: 57.5M
- License: Apache-2.0

## Runtime test results for @humanfs/core@0.19.2

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

| Runtime | require("@humanfs/core") | import "@humanfs/core" |
|---|---|---|
| Node.js 18 | fails (ERR_PACKAGE_PATH_NOT_EXPORTED) | works |
| Node.js 20 | fails (ERR_PACKAGE_PATH_NOT_EXPORTED) | works |
| Node.js 22 | fails (ERR_PACKAGE_PATH_NOT_EXPORTED) | works |
| Node.js 24 | fails (ERR_PACKAGE_PATH_NOT_EXPORTED) | works |
| Node.js 26 | fails (ERR_PACKAGE_PATH_NOT_EXPORTED) | works |
| Bun 1.4.0 | fails (Error) | works |

## How to import @humanfs/core

ES modules:

```js
import * as core from "@humanfs/core";
```

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

CommonJS:

```js
// require("@humanfs/core") failed in our probe on Node.js 20.19+, 22.12+ and newer as well (ERR_PACKAGE_PATH_NOT_EXPORTED); see the runtime table.

// Any Node.js version the package supports (>=18.18.0), from an async function:
async function main() {
  const core = await import("@humanfs/core");
}
```

## Module format by version

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

| Versions | Format | First published |
|---|---|---|
| 0.6.0 – 0.19.2 | ESM-only | Jan 30, 2024 |

## Frequently asked

**Is @humanfs/core ESM-only?**

@humanfs/core@0.19.2 is ESM-only. @humanfs/core has been ESM-only since its first stable release; there is no CommonJS version to pin.

**Which version of @humanfs/core still supports CommonJS / require()?**

None. @humanfs/core has always been ESM-only. Use import, or a dynamic import("@humanfs/core") from an async function in CommonJS.

**How do I use @humanfs/core from a CommonJS file?**

From a CommonJS file, use a dynamic import inside an async function: const core = await import("@humanfs/core"). That works on every Node.js version the package supports (>=18.18.0). require("@humanfs/core") failed in our probe on Node.js 20+ as well; see the runtime table for the error before relying on it.

**Does @humanfs/core work in Bun?**

Yes. import "@humanfs/core" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

**Does @humanfs/core ship TypeScript types?**

Yes. @humanfs/core bundles its own type declarations; no @types package is needed.

## Links

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